USE_PM_CLK_RUNTIME_OPS is introduced so we don't repeat the same code
to do runtime_suspend and runtime_resume across users of PM clocks.
Use it to remove the boilerplate code.
Signed-off-by: Rajendra Nayak
Reviewed-by: Kevin Hilman
Acked-by: Santosh Shilimkar
Acked-by: Geert Uytterh
USE_PM_CLK_RUNTIME_OPS is introduced so we don't repeat the same code
to do runtime_suspend and runtime_resume across users of PM clocks.
Use it to remove the boilerplate code.
Signed-off-by: Rajendra Nayak
Reviewed-by: Kevin Hilman
Acked-by: Santosh Shilimkar
Acked-by: Geert Uytterh
Most users of PM clocks do the extact same things in the runtime
suspend/resume callbacks. Provide them USE_PM_CLK_RUNTIME_OPS so
as to avoid/remove boilerplate code.
Signed-off-by: Rajendra Nayak
Reviewed-by: Kevin Hilman
Acked-by: Santosh Shilimkar
Acked-by: Geert Uytterhoeven
---
drivers
USE_PM_CLK_RUNTIME_OPS is introduced so we don't repeat the same code
to do runtime_suspend and runtime_resume across users of PM clocks.
Use it to remove the boilerplate code.
Signed-off-by: Rajendra Nayak
Reviewed-by: Kevin Hilman
Acked-by: Santosh Shilimkar
Acked-by: Geert Uytterh
Most users of PM clocks do the exact same thing in runtime callbacks.
Provide default callbacks and cleanup the existing users (keystone/davinci
/omap1/sh)
Rajendra Nayak (5):
PM / clock_ops: Provide default runtime ops to users
arm: keystone: remove boilerplate code and use
USE_PM_CLK_RUNTIME_OPS is introduced so we don't repeat the same code
to do runtime_suspend and runtime_resume across users of PM clocks.
Use it to remove the boilerplate code.
Signed-off-by: Rajendra Nayak
Reviewed-by: Kevin Hilman
Acked-by: Santosh Shilimkar
Acked-by: Geert Uytterh
> On Tue, Apr 21, 2015 at 1:25 AM, santosh shilimkar
> wrote:
>> On 4/20/2015 4:21 PM, Kevin Hilman wrote:
>>>
>>> Rajendra Nayak writes:
>>>
>>>> Most users of PM clocks do the exact same thing in runtime callbacks.
>>>
>
USE_PM_CLK_RUNTIME_OPS is introduced so we don't repeat the same code
to do runtime_suspend and runtime_resume across users of PM clocks.
Use it to remove the boilerplate code.
Signed-off-by: Rajendra Nayak
---
drivers/sh/pm_runtime.c | 47 ++-
1
USE_PM_CLK_RUNTIME_OPS is introduced so we don't repeat the same code
to do runtime_suspend and runtime_resume across users of PM clocks.
Use it to remove the boilerplate code.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap1/pm_bus.c | 37 ++---
1
USE_PM_CLK_RUNTIME_OPS is introduced so we don't repeat the same code
to do runtime_suspend and runtime_resume across users of PM clocks.
Use it to remove the boilerplate code.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-davinci/pm_domain.c | 32 +---
1
USE_PM_CLK_RUNTIME_OPS is introduced so we don't repeat the same code
to do runtime_suspend and runtime_resume across users of PM clocks.
Use it to remove the boilerplate code.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-keystone/pm_domain.c | 33 +
1
Most users of PM clocks do the exact same thing in runtime callbacks.
Provide default callbacks and cleanup the existing users
(keystone/davinci/omap1/sh)
Rajendra Nayak (5):
PM / clock_ops: Provide default runtime ops to users
arm: keystone: remove boilerplate code and use
Most users of PM clocks do the extact same things in the runtime
suspend/resume callbacks. Provide them USE_PM_CLK_RUNTIME_OPS so
as to avoid/remove boilerplate code.
Signed-off-by: Rajendra Nayak
---
drivers/base/power/clock_ops.c | 38 ++
include/linux
am I
> ---
> Changes from v1:
> * changed the clock domain to "pcie_clkdm"
> * Added PCIe as a slave port for l3_main.
Looks good to me,
Reviewed-by: Rajendra Nayak
>
> Boot log for dra7xx can be found at http://paste.ubuntu.com/7769402/
>
On Friday 09 May 2014 06:07 PM, Sekhar Nori wrote:
> From: Lokesh Vutla
>
> RTCSS on DRA7 provides a precise real-time clock.
> Add hwmod entry for this IP.
>
> Signed-off-by: Lokesh Vutla
> Signed-off-by: Sekhar Nori
Reviewed-by: Rajendra Nayak
> ---
> Appli
On Tuesday 27 May 2014 02:25 PM, Rajendra Nayak wrote:
> Without the patch:
> /debug/.../dpll_core_x2_ck/dpll_core_h12x2_ck # cat clk_rate
> 53200
> /debug/.../dpll_core_x2_ck/dpll_core_h12x2_ck/l3_iclk_div # cat clk_rate
> 53200
> /debug/.../dpll_core_x2_ck/dpll_core_h1
> Correct .mpu_rt_idx to 1 as the module register space (SYSCONFIG..)
> is passed as the second memory resource in the device tree.
>
> Signed-off-by: Roger Quadros
> Tested-by: Roger Quadros
Reviewed-by: Rajendra Nayak
> ---
> arch/arm/mach-omap2/omap_hwmod_7xx_data.c |
On Thursday 19 June 2014 01:20 AM, Roger Quadros wrote:
> This module is needed for the SATA and PCIe PHYs.
>
> Signed-off-by: Roger Quadros
> Tested-by: Roger Quadros
Reviewed-by: Rajendra Nayak
> ---
> v2:
> - added .main_clk to hwmod.
> - moved interface stru
On Wednesday 25 June 2014 11:32 PM, Kishon Vijay Abraham I wrote:
> Added hwmod data for pcie1 and pcie2 subsystem present in DRA7xx SOC.
>
> Cc: Tony Lindgren
> Cc: Russell King
> Cc: Paul Walmsley
> Signed-off-by: Kishon Vijay Abraham I
> Tested-by: Kishon Vijay Abraham I
> ---
> Please fin
gt; Cc: Paul Walmsley
> Signed-off-by: Kishon Vijay Abraham I
> Tested-by: Kishon Vijay Abraham I
Looks good to me, feel free to add
Reviewed-by: Rajendra Nayak
> ---
> Please find the bootlog with these hwmod patches
> http://paste.ubuntu.com/7701601/
> arch/arm/mach-omap2/
On Wednesday 18 June 2014 05:46 PM, Roger Quadros wrote:
> This module is needed for the SATA and PCIe PHYs.
>
> Signed-off-by: Roger Quadros
> Tested-by: Roger Quadros
> ---
> arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 25 +
> 1 file changed, 25 insertions(+)
>
> diff
y: Roger Quadros
verified against TRM version vP, looks good to me.
Reviewed-by: Rajendra Nayak
>> ---
>> arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 12
>> 1 file changed, 12 insertions(+)
>>
>> diff --git a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c
>
On Wednesday 18 June 2014 01:32 PM, Roger Quadros wrote:
> On 04/23/2014 08:35 PM, Roger Quadros wrote:
>> From: Nikhil Devshatwar
>>
>> Add hwmods for ocp2scp3 and sata modules.
>From what I see this is actually adding the ocp2scp3 data and fixing up some
of the sata data which is already added
On Monday 26 May 2014 04:14 PM, Archit Taneja wrote:
> Generally, IP blocks/modules within a clock domain each have their own
> CM_x_CLKCTRL register, each having it's own MODULEMODE field to manage the
> module.
>
> DSS clockdoain, however, has multiple modules in it, but only one register
> name
divider clock,
with the default divider set to 2. l4 then derived from l3 is a fixed factor
clock, but the fixed divider is 2 and not 1. Which means the l3 clock is
half of core DPLLs h12x2 and l4 is half of l3 (as seen with this patch)
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/dra7xx
On Tuesday 20 May 2014 11:01 AM, Archit Taneja wrote:
> Hi,
>
> On Friday 16 May 2014 01:44 PM, Tomi Valkeinen wrote:
>> On 12/05/14 18:48, Tony Lindgren wrote:
>>
> Also, I'm wondering why we still have .clk and .opt_clks entries in the
> hwmod data for am43xx and omap5 which are both dev
opt_clks
for all such instances.
The modules (like GPIO and DSS) which do have this need to handle optional
clocks during a ocp softreset are marked with a flag
'HWMOD_CONTROL_OPT_CLKS_IN_RESET'
so its easy to identify the ones which don't have this requirement.
Signed-off-by:
On Monday 19 May 2014 08:57 PM, Nishanth Menon wrote:
> Currently the files in /sys/devices/soc0/ show no information about
> DRA7. Few userspace programs do depend on this information to make SoC
> specific support. So update logic to detect the relevant information and
> provide to userspace.
>
On Monday 19 May 2014 04:40 PM, Tomi Valkeinen wrote:
> On 19/05/14 13:28, Rajendra Nayak wrote:
>
>> Yeah, thats what it looks like to me. l3_gclk is the 200Mhz clock derived
>> from
>> core-m4 post divider and l3s_gclk/l4ls_gclk are half of that at 100Mhz,
>> de
On Monday 19 May 2014 03:42 PM, Tomi Valkeinen wrote:
> On 19/05/14 12:24, Rajendra Nayak wrote:
>> On Friday 09 May 2014 05:26 PM, Tomi Valkeinen wrote:
>>> From: Sathya Prakash M R
>>>
>>> Add DSS hwmod data for AM43xx.
>>>
>>> Sign
On Friday 09 May 2014 05:26 PM, Tomi Valkeinen wrote:
> From: Sathya Prakash M R
>
> Add DSS hwmod data for AM43xx.
>
> Signed-off-by: Sathya Prakash M R
> Signed-off-by: Tomi Valkeinen
> ---
> arch/arm/mach-omap2/omap_hwmod_43xx_data.c | 104
> +
> arch/arm/mach-
On Thursday 08 May 2014 05:34 PM, Javier Martinez Canillas wrote:
> Hello Rajendra,
>
> On Thu, May 8, 2014 at 1:10 PM, Rajendra Nayak wrote:
>> On Thursday 08 May 2014 02:56 PM, Javier Martinez Canillas wrote:
>>> Hello Rajendra,
>>>
>>> On Thu, May
On Thursday 08 May 2014 02:56 PM, Javier Martinez Canillas wrote:
> Hello Rajendra,
>
> On Thu, May 8, 2014 at 9:06 AM, Rajendra Nayak wrote:
>> On Wednesday 23 April 2014 11:41 AM, Rajendra Nayak wrote:
>>> Replace the clk_enable()s with a clk_prepare_enable() and
>&g
On Wednesday 23 April 2014 11:41 AM, Rajendra Nayak wrote:
> Replace the clk_enable()s with a clk_prepare_enable() and
> the clk_disables()s with a clk_disable_unprepare()
>
> This never showed issues due to the OMAP platform code (hwmod)
> leaving these clocks in clk_prepare()ed s
On Thursday 08 May 2014 05:38 AM, Paul Walmsley wrote:
> Hi Rajendra,
>
> On Wed, 23 Apr 2014, Rajendra Nayak wrote:
>
>> The patches fix some opt clock handling in gpio and in
>> hwmod.
>>
>> Rajendra Nayak (2):
>> gpio: omap: prepare and unprepare
On Tuesday 06 May 2014 09:58 PM, Tony Lindgren wrote:
> * Rajendra Nayak [140429 04:22]:
>> On Tuesday 29 April 2014 04:48 PM, Arnd Bergmann wrote:
>>> On Tuesday 29 April 2014 16:35:13 Rajendra Nayak wrote:
>>>> @@ -393,7 +395,12 @@ IS_OMAP_TYPE(3430, 0x
On Tuesday 29 April 2014 04:35 PM, Rajendra Nayak wrote:
> changes in v4:
> -1- used full SoC names in compatibles eg "ti,dra742" and "ti,dra722"
> -2- Created a seperate patch for replacing __initdata with __initconst
>
> changes in v3:
> Removed wildcards
On Tuesday 29 April 2014 04:48 PM, Arnd Bergmann wrote:
> On Tuesday 29 April 2014 16:35:13 Rajendra Nayak wrote:
>> @@ -393,7 +395,12 @@ IS_OMAP_TYPE(3430, 0x3430)
>>
>> #if defined(CONFIG_SOC_DRA7XX)
>> #undef soc_is_dra7xx
>> +#undef soc_is_dra74x
>
The only difference from the dra74x devices is the missing .smp entry.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/board-generic.c | 25 +
1 file changed, 21 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-omap2/board-generic.c
b/arch/arm/mach
Use of const init definition must use __initconst so replace
all such instances where __initdata is used.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/board-generic.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/arch/arm/mach-omap2
Use the corresponding compatibles to identify the devices.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/soc.h |7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/mach-omap2/soc.h b/arch/arm/mach-omap2/soc.h
index 30abcc8..5ff724e 100644
--- a/arch/arm/mach-omap2
DRA72x devices are single core Cortex A15 devices belonging to the
DRA7 family (Similar to the DRA74x devices which are dual core Cortex
A15 based)
The patches (based off 3.15-rc3) add minimal DT/kernel modifications to add
boot support on DRA722 device reusing all the kernel data for DRA742 device
"ti,dra752" is neither documented nor correct, since the device is actually a
dra742 device as rightly documented in dt bindings.
Signed-off-by: Rajendra Nayak
Cc: devicet...@vger.kernel.org
---
arch/arm/boot/dts/dra7-evm.dts |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
DRA722 is part of DRA72x family which are single core cortex A15 devices
with most infrastructure IPs otherwise same as whats on the DRA74x family.
So move the cpu nodes into dra74x.dtsi and dra72x.dtsi respectively.
Also add a minimal dra72-evm dts file.
Signed-off-by: Rajendra Nayak
Cc
On Monday 28 April 2014 02:20 PM, Arnd Bergmann wrote:
> On Monday 28 April 2014 11:39:22 Rajendra Nayak wrote:
>>
>> DRA742 EVM: Software Developement Board for DRA742
>> compatible = "ti,dra7-evm", "ti,dra742", "ti,dra74", "ti,dr
out the __initdata to __initconst change for existing ones into a
> different patch, and limit this patch to just what the patch subject says.
Sure, I will, if that helps.
>
> regards
> Suman
>
>>
>> Signed-off-by: Rajendra Nayak
>> ---
>> arch/arm/ma
On Thursday 24 April 2014 06:43 PM, Arnd Bergmann wrote:
> On Thursday 24 April 2014, Rajendra Nayak wrote:
>>
>> -- DRA742
>> - compatible = "ti,dra7xx", "ti,dra7"
>> +- DRA74x
>> + compatible = "ti,dra74", "ti,dra7"
>&
) add minimal DT/kernel modifications to add
boot support for DRA72x devices reusing all the kernel data for DRA74x devices.
Rajendra Nayak (4):
ARM: dts: dra7-evm: Remove the wrong and undocumented compatible
ARM: dts: Add support for DRA72x family of devices
ARM: OMAP2+: Add machine entry
DRA72x is a single core cortex A15 device with most infrastructure IPs otherwise
same as whats on the DRA74x devices.
So move the cpu nodes into dra74x.dtsi and dra72x.dtsi respectively.
Also add a minimal dra72-evm dts file.
Signed-off-by: Rajendra Nayak
Cc: linux-...@vger.kernel.org
Cc
"ti,dra752" is neither documented nor correct, since the device is actually a
dra742 device as rightly documented in dt bindings.
Signed-off-by: Rajendra Nayak
Cc: devicet...@vger.kernel.org
---
arch/arm/boot/dts/dra7-evm.dts |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Use the corresponding compatibles to identify the devices.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/soc.h |7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/mach-omap2/soc.h b/arch/arm/mach-omap2/soc.h
index 30abcc8..5ff724e 100644
--- a/arch/arm/mach-omap2
[] __initdata = {
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/board-generic.c | 45 ---
1 file changed, 31 insertions(+), 14 deletions(-)
diff --git a/arch/arm/mach-omap2/board-generic.c
b/arch/arm/mach-omap2/board-generic.c
index b8920b6..dabb9f6 100644
On Wednesday 23 April 2014 03:21 PM, Arnd Bergmann wrote:
> On Wednesday 23 April 2014 14:32:54 Rajendra Nayak wrote:
>>
>> #ifdef CONFIG_SOC_DRA7XX
>> -static const char *dra7xx_boards_compat[] __initdata = {
>> +static const char *dra74x_boards_compat[] __initcons
DRA72x is a single core cortex A15 device with most infrastructure IPs otherwise
same as whats on the DRA74x devices.
So move the cpu nodes into dra74x.dtsi and dra72x.dtsi respectively.
Also add a minimal dra72-evm dts file.
Signed-off-by: Rajendra Nayak
Cc: linux-...@vger.kernel.org
Cc
Use the corresponding compatibles to identify the devices.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/soc.h |7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/mach-omap2/soc.h b/arch/arm/mach-omap2/soc.h
index 30abcc8..b8a4834 100644
--- a/arch/arm/mach-omap2
"ti,dra752" is neither documented nor correct, since the device is actually a
dra742 device as rightly documented in dt bindings.
Signed-off-by: Rajendra Nayak
Cc: devicet...@vger.kernel.org
---
arch/arm/boot/dts/dra7-evm.dts |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[] __initdata = {
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/board-generic.c | 46 +--
1 file changed, 33 insertions(+), 13 deletions(-)
diff --git a/arch/arm/mach-omap2/board-generic.c
b/arch/arm/mach-omap2/board-generic.c
index b8920b6..4d1222d 100644
devices.
Rajendra Nayak (4):
ARM: dts: dra7-evm: Remove the wrong and undocumented compatible
ARM: dts: Add support for DRA72x family of devices
ARM: OMAP2+: Add machine entry for dra72x devices
ARM: DRA7: Add support for soc_is_dra74x() and soc_is_dra72x()
varients
.../devicetree
On Friday 14 March 2014 02:50 PM, Rajendra Nayak wrote:
> DRA752 device is wrongly documented as DRA742 device. Fix the typo.
Thanks to Nishanth for pointing out that the device part number is infact
DRA742. The compatible sting infact seems to have a typo. I'll fix
that up a post a v2
Replace the clk_enable()s with a clk_prepare_enable() and
the clk_disables()s with a clk_disable_unprepare()
This never showed issues due to the OMAP platform code (hwmod)
leaving these clocks in clk_prepare()ed state by default.
Reported-by: Kishon Vijay Abraham I
Signed-off-by: Rajendra Nayak
At hwmod init, theres no reason why optional clocks should be left in
clk_prepare()ed state as these are actually directly controlled by the
drivers themselves. Let the drivers prepare/unprepare as well as enable/
disable them.
Signed-off-by: Rajendra Nayak
Cc: Benoit Cousson
---
arch/arm/mach
The patches fix some opt clock handling in gpio and in
hwmod.
Rajendra Nayak (2):
gpio: omap: prepare and unprepare the debounce clock
ARM: OMAP2+: hwmod: Don't leave the optional clocks in
clk_prepare()ed state
arch/arm/mach-omap2/omap_hwmod.c | 13 ++---
drivers/gpio
On Saturday 15 March 2014 07:51 AM, Suman Anna wrote:
> Hi Rajendra,
>
> On 03/14/2014 04:20 AM, Nayak, Rajendra wrote:
>> The only difference from the dra75x devices is the missing .smp entry.
>>
>> Signed-off-by: Rajendra Nayak
>> ---
>> arc
The only difference from the dra75x devices is the missing .smp entry.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/board-generic.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/arch/arm/mach-omap2/board-generic.c
b/arch/arm/mach-omap2/board-generic.c
index
DRA72x is a single core cortex A15 device with most infrastructure IPs otherwise
same as whats on the DRA75x devices.
So move the cpu nodes into dra75x.dtsi and dra72x.dtsi respectively.
Also add a minimal dra72-evm dts file.
Signed-off-by: Rajendra Nayak
---
.../devicetree/bindings/arm/omap
DRA72x devices are single core Cortex A15 devices belonging to the
DRA7 family (Similar to the DRA75x devices which are dual core Cortex
A15 based)
The patches add minimal DT/kernel modifications to add boot support for
DRA72x devices resuing all the kernel data for DRA75x devices.
Rajendra
DRA752 device is wrongly documented as DRA742 device. Fix the typo.
Signed-off-by: Rajendra Nayak
---
.../devicetree/bindings/arm/omap/omap.txt |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/omap/omap.txt
b
94220.html
[2] http://www.spinics.net/lists/linux-omap/msg98490.html
Cc: Nishanth Menon
Signed-off-by: Rajendra Nayak
Signed-off-by: Suman Anna
Signed-off-by: Lokesh Vutla
---
arch/arm/mach-omap2/omap_hwmod.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/
On Monday 17 February 2014 04:45 AM, Vaibhav Bedia wrote:
> Use the correct register offset for issuing the
> reset command in OMAP5. Since dev_inst is set dynamically
> OMAP4 should not be affected by this change.
>
> Signed-off-by: Vaibhav Bedia
Acked-by: Rajendra Nayak
>
On Friday 14 February 2014 04:49 AM, Tony Lindgren wrote:
> * Lokesh Vutla [140207 02:24]:
>> From: Rajendra Nayak
>>
>> The SyncTimer in AM43x is clocked using the following two sources:
>> 1) An inaccuarte 32k clock (CLK_32KHZ) derived from PER DPLL, causing system
&
[]..
>>> so a bit more work is needed. Maybe also rebase these against
>>> omap-for-v3.14/dt too?
>>
>> Will do.
>
> Rebased on top of omap-for-v3.14/omap3-board-removal. Patches are on my
> k.org tree:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git wip/omap-fix-intc
It needs a
On Friday 20 December 2013 03:59 PM, Tero Kristo wrote:
> On 12/20/2013 12:07 PM, Rajendra Nayak wrote:
>> On Friday 20 December 2013 12:32 AM, Tero Kristo wrote:
>>> On 12/19/2013 08:26 PM, Tony Lindgren wrote:
>>>> * Tero Kristo [131219 03:26]:
>>>>&g
On Friday 20 December 2013 12:32 AM, Tero Kristo wrote:
> On 12/19/2013 08:26 PM, Tony Lindgren wrote:
>> * Tero Kristo [131219 03:26]:
>>> Divider clock can now be registered to use low level register access ops.
>>> Preferred initialization method is via clock description.
>>
>> This seems to ma
With clocks for OMAP moving to DT, its now possible to pass all optional clock
data for each device from DT instead of having it in hwmod.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/omap_hwmod.c | 65 --
1 file changed, 63 insertions(+), 2
With support to parse clock data from DT, move all main and optional
clock information from hwmod to DT.
We still retain clocks in hwmod for devices which do not have a DT node.
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/omap4.dtsi | 100 +++
arch
sg95746.html
[2] http://www.spinics.net/lists/devicetree/msg13455.html
[3] http://www.spinics.net/lists/arm-kernel/msg288036.html
[4] http://www.spinics.net/lists/arm-kernel/msg288023.html
Rajendra Nayak (3):
ARM: OMAP2+: Add support to parse 'main_clk' info from DT
ARM: OMAP2+: Add suppo
With clocks for OMAP moving to DT, its now possible to pass the 'main_clk'
data for each device from DT instead of having it in hwmod.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/omap_hwmod.c | 23 +--
1 file changed, 17 insertions(+), 6 deletions(-)
M
where we use uart1 for console, boot fails with DEBUG_LL enabled.
Reported-by: Lokesh Vutla
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/omap_hwmod_7xx_data.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_7xx_data.c
b/arch/arm/
ll (see line 105)
So, fix the unchecked dereference of arch_pwrdm.
Reported-by: Dan Carpenter
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/powerdomain.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-omap2/powerdomain.c
b/arch/arm/mach-oma
On Tuesday 05 November 2013 06:44 PM, Sricharan R wrote:
> Enable the crossbar IP support for DRA7xx soc.
>
> Cc: Santosh Shilimkar
> Cc: Rajendra Nayak
> Cc: Tony Lindgren
> Signed-off-by: Sricharan R
> ---
> arch/arm/mach-omap2/Kconfig|1 +
> arch/ar
On Monday 21 October 2013 05:56 PM, Mike Turquette wrote:
> Quoting Paul Walmsley (2013-10-19 10:16:50)
>> On Fri, 11 Oct 2013, Tero Kristo wrote:
>>
>>> Some drivers require direct access to the autoidle functionality of the
>>> interface clocks. Added clock APIs for these, so that the drivers do
AM
> series SoCs, where i2c is defined.
Thanks Nishanth.
Acked-by: Rajendra Nayak
>
> V1: https://patchwork.kernel.org/patch/3046671/
>
> Nishanth Menon (2):
> ARM: dts: OMAP3+: Add i2c aliases
> ARM: dts: AM33xx+: Add i2c aliases
>
> arch/arm/boot/dts/am3
nsistent manner to fix the same if the i2c dev interface have no
> consistent numbering. Provide alias to allow ordering the i2c devices
> correctly.
This looks good Nishanth. Shouldn't we just go ahead and fix these for
all OMAPs/AMxx devices which would have the same problem as OMAP5
On Tuesday 15 October 2013 12:57 PM, Benoit Cousson wrote:
> Hi Rajendra,
>
> On 09/10/2013 18:45, Benoit Cousson wrote:
>> + A couple of DT maintainers
>>
>> On 09/10/2013 18:41, Rajendra Nayak wrote:
>>> On Wednesday 09 October 2013 08:43 PM, Benoit Cousson w
On Tuesday 08 October 2013 11:45 PM, Tony Lindgren wrote:
> * Rajendra Nayak [131003 23:50]:
>> On Tuesday 01 October 2013 12:34 PM, Afzal Mohammed wrote:
>>> Hi Paul, Benoit, Tony,
>>>
>>> This series adds PRCM support (except clock tree) for AM43x SoC'
On Wednesday 09 October 2013 08:43 PM, Benoit Cousson wrote:
> Hi Rajendra,
>
> On 09/10/2013 12:11, Rajendra Nayak wrote:
>> On OMAP we have co-processor IPs, memory controllers,
>> GPIOs which control regulators and power switches to
>> PMIC, and SoC internal Bus
as part of GPMC driver
in the kernel, and hence the flag is left as is in hwmod, which can be
removed once the driver does what its expected to.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/omap_hwmod_33xx_data.c |4 ++--
arch/arm/mach-omap2/omap_hwmod_44xx_data.c |4 +---
arch
For modules/IPs/hwmods which do not have
-1- sys->class->reset()
and
-2- hardreset lines
and
-3- No way to do an ocp reset (no sysc control)
the flag 'HWMOD_INIT_NO_RESET' is not much useful.
Cleanup all such instances across various hwmod data files.
Signed-off-by: Rajendra Naya
pass this information from DT.
Update the am33xx/omap4 and omap5 dtsi files with the
new bindings for modules which either should not be
idled. reset or both. A later patch would cleanup the
same information that exists today as part of the hwmod
data files.
Signed-off-by: Rajendra Nayak
Now that we have DT bindings to specify which devices should not
be reset and idled during init, make hwmod extract the information
(and store them in internal flags) from Device tree.
Signed-off-by: Rajendra Nayak
---
arch/arm/mach-omap2/omap_hwmod.c | 23 ---
1 file
Do not reset GPIO0 at boot-up because GPIO0 is used
on AM335x EVM-SK to control VTT regulators on DDR3.
Without this EVM-SK boards fail to boot-up because
of DDR3 corruption.
Signed-off-by: Rajendra Nayak
---
arch/arm/boot/dts/am335x-evmsk.dts |4
1 file changed, 4 insertions
OMAP4 panda es, AM335x EVM and AM335x EVM-SK
[1] http://www.mail-archive.com/linux-omap@vger.kernel.org/msg94349.html
Rajendra Nayak (5):
ARM: OMAP2+: hwmod: cleanup HWMOD_INIT_NO_RESET usage
ARM: dts: omap: Add new bindings for OMAP
ARM: OMAP2+: hwmod: Extract no-idle and no-reset info from DT
On Wednesday 09 October 2013 01:49 PM, Benoit Cousson wrote:
> Hi Rajendra,
>
> On 09/10/2013 09:37, Rajendra Nayak wrote:
>> On Wednesday 09 October 2013 12:54 PM, Paul Walmsley wrote:
>>> Hi Benoît, Rajendra,
>>>
>>> On Tue, 20 Aug 2013, Rajendra
On Wednesday 09 October 2013 12:54 PM, Paul Walmsley wrote:
> Hi Benoît, Rajendra,
>
> On Tue, 20 Aug 2013, Rajendra Nayak wrote:
>
>> Now that we have DT bindings to specify which devices on the SoC should not
>> be reset or idled, get rid of the same information
M43x
> 2. omap_hwmod_33xx_43xx_ipblock_data.c has the common hwmod structs
>shared between AM335x and AM43x
This split and reuse looks much better and readable now.
For the complete series,
Acked-by: Rajendra Nayak
> 3. Instances where clock domain or clock topology has changed in t
On Thursday 29 August 2013 10:50 PM, Kevin Hilman wrote:
> Rajendra Nayak writes:
>
>> In order to handle errata I688, a page of sram was reserved by doing a
>> static iotable map. Now that we use gen_pool to manage sram, we can
>> completely remove all of these
[]..
> +
> +#define pr_fmt(fmt) "%s: " fmt, __func__
> +
> +#ifdef DEBUG
> +#define prn(num) printk(#num "=%d\n", num)
> +#define prx(num) printk(#num "=%x\n", num)
> +#else
> +#define prn(num) do { } while (0)
> +#define prx(num) do { } while (0)
> +#endif
> +
> +#include
> +#include
> +#inclu
On Thursday 29 August 2013 06:53 PM, Santosh Shilimkar wrote:
> On Thursday 29 August 2013 07:23 AM, Rajendra Nayak wrote:
>> In order to handle errata I688, a page of sram was reserved by doing a
>> static iotable map. Now that we use gen_pool to manage sram, we can
>> com
On Thursday 29 August 2013 07:01 PM, Santosh Shilimkar wrote:
> On Thursday 29 August 2013 09:26 AM, Sekhar Nori wrote:
>> On 8/29/2013 4:53 PM, Rajendra Nayak wrote:
>>> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
>>> index 22d9f2b..1ba6a7
X's
> ocp interface list.
You need to swap patches 5/6 and 6/6 to maintain git-bisect.
Thats needed because after $subject patch, hwmod wouldn't find
the register iospace and crash, and thats added only in patch 6/6.
regards,
Rajendra
>
> Cc: Rajendra Nayak
> Cc: Sricharan R
1 - 100 of 1421 matches
Mail list logo
