Hi Paul,
...
Well after the UART timeouts expired, I do not see any powerdomains
transitioning from ON.
What's even more strange is that the same thing is working fine on all
the other OMAP3 platforms I tested: 3430/n900, 3630/zoom3 and even a
different 3530-based platform, the OMAP3EVM.
I tr
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Tony Lindgren
> Sent: Tuesday, March 29, 2011 3:51 AM
> To: linux-arm-ker...@lists.infradead.org
> Cc: linux-omap@vger.kernel.org
> Subject: [PATCH 01/10] omap: Use separa
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:31 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-deb
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Tony Lindgren
> Sent: Tuesday, March 29, 2011 3:51 AM
> To: linux-arm-ker...@lists.infradead.org
> Cc: linux-omap@vger.kernel.org
> Subject: [PATCH 01/10] omap: Use separa
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:31 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-deb
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Tony Lindgren
> Sent: Tuesday, March 29, 2011 3:51 AM
> To: linux-arm-ker...@lists.infradead.org
> Cc: linux-omap@vger.kernel.org
> Subject: [PATCH 01/10] omap: Use separa
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:31 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-deb
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
Hi,
>-Original Message-
>From: Tony Lindgren [mailto:t...@atomide.com]
>Sent: Tuesday, March 29, 2011 2:50 AM
>To: Hema HK
>Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org
>Subject: Re: [PATCH 1/2 v2] usb: otg: OMAP4430: Fixing the
>omap4430_phy_init function
>
>* Hema HK [11032
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Tony Lindgren
> Sent: Tuesday, March 29, 2011 3:51 AM
> To: linux-arm-ker...@lists.infradead.org
> Cc: linux-omap@vger.kernel.org
> Subject: [PATCH 01/10] omap: Use separa
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:31 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-deb
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:31 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-deb
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:31 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-deb
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:31 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-deb
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:31 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-deb
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:31 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-deb
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:31 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-deb
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
As a part of Voltage Layer Cleanup Patches,
submitted by Kevin Hilman, Voltage domain
Information is removed from hwmod,
So the patch removes 'vdd_name' info from omap_hwmod
and adds that info into dev_attr as SR code uses vdd_name
to get voltagedomain sructure info.
Tested on OMAP3630 SDP and OMA
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:31 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-deb
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:31 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-deb
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:31 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-deb
Hi,
> -Original Message-
> From: Jokiniemi Kalle (Nokia-MS/Tampere)
> > > diff --git a/include/linux/power/isp1704_charger.h
> > b/include/linux/power/isp1704_charger.h
> > > new file mode 100644
> > > index 000..68096a6
> > > --- /dev/null
> > > +++ b/include/linux/pow
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:31 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 14/21] OMAP4: pm-deb
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
> -Original Message-
> From: Tony Lindgren [mailto:t...@atomide.com]
> Sent: Tuesday, March 29, 2011 2:20 AM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; rna...@ti.com;
> linux-arm-ker...@lists.infradead.org
> Subject: Re: [pm-core][PATCH v3 01/21] OMAP4: PM: Ad
The DSI protocol engine has no interrupt for signalling the end of a Frame
transfer. The present approach is to send a BTA after DISPC generates a
FRAMEDONE interrupt, and unlock the dsi bus only when the BTA Ack is received.
The assumption made with this approach was that OMAP will send a BTA onl
We can keep everything sys_timer and gptimer.c related code in
timer.c as the code will be very minimal.
Later on we can also remove timer-mpu.c, as it can be called from
omap4_timer_init function.
This allows us to get rid of confusing existing files. We currently
have timer-gp.c, timer-mpu.c, a
This is no longer needed as we now just set the desired
.timer in MACHINE_START. We can now also remove timer-gp.h.
Signed-off-by: Tony Lindgren
---
arch/arm/mach-omap2/board-4430sdp.c|4
arch/arm/mach-omap2/board-devkit8000.c |4
arch/arm/mach-omap2/board-omap3beag
Use dmtimer macros for clocksource. As with the clockevent,
this allows us to initialize the rest of dmtimer code later on.
Note that eventually we will be initializing the timesource
from init_early so sched_clock will work properly for
CONFIG_PRINTK_TIME.
Signed-off-by: Tony Lindgren
---
arch
There's no need to initialize the dmtimer framework early.
Just mark the clocksource and timesource as reserved, and
initialize dmtimer with an arch_initcall.
Signed-off-by: Tony Lindgren
---
arch/arm/mach-omap1/timer32k.c|4
arch/arm/mach-omap2/timer-gp.c|9
This removes the support for setting the wake-up timer for debugging.
Later on we can reserve gptimer1 for PM code only and have similar
functionality.
Signed-off-by: Tony Lindgren
---
arch/arm/mach-omap2/pm-debug.c | 27 ---
arch/arm/mach-omap2/pm.h |6 -
This patch makes timer-gp.c to use only a subset of dmtimer
functions without the need to initialize dmtimer code early.
Note that omap_dmtimer_init_one can eventually be moved to
omap2+ specific dmtimer.c.
Also note that now with the inline functions, timer_set_next_event
becomes more efficient
This will allow us to share the code between system timer and
dmtimer device driver code without having to initialize all
dmtimers early. It will also make the timer_set_next_event
more efficient as the inline functions will optimize the code
better in this case.
Signed-off-by: Tony Lindgren
---
These will be needed when dmtimer platform init code gets split
for omap1 and omap2+. These will also be needed for inline macros
for sys_timer in the following patches. No functional changes.
Signed-off-by: Tony Lindgren
---
arch/arm/plat-omap/dmtimer.c | 121 -
This is needed for the following patches to initialize non-sys_timer
hardware later on. Again, there's no need to do cpu_is_omap calls
as we only care about the major omap generation. We can do this with
the .timer entry alone.
Note that for now we just set stubs for the various sys_timer
entries
This allows us to remove cpu_is_omap calls from init_irq functions
and the irq handler. There should not be any need for cpu_is_omap
as at this point we only care about SoC generation, and not about
subcategories.
The main reason for the patch is that we want to initialize only
minimal omap specif
Hi all,
This series continues the work to only initialize minimal omap code
in init_early and to cut down dependencies to code that should be
initialized later. It also cleans up the omap2+ timer init code to prepare
things for the later patches.
After this series further patches can make the dmt
* Hema HK [110324 04:36]:
> omap4430_phy_init() function can be called with no device pointer,
> to powerdown the PHY during board init when USB is disabled.
> Fix the function accordingly.
This should no longer be needed after merge commit
0df0914d414a504b975f3cc66ace0c16ef55b7f3.
Tony
--
To un
* Hema HK [110324 04:03]:
> omap4430_phy_init() function can be called with no device pointer
> to powerdown the UTMI PHY during board init when USB is disabled.
> Fix the function accordingly.
I don't think this is the case any longer, see merge commit
0df0914d414a504b975f3cc66ace0c16ef55b7f3.
* Tomi Valkeinen [110323 00:43]:
> On Tue, 2011-03-22 at 13:49 -0500, Felipe Contreras wrote:
> > On Mon, Mar 21, 2011 at 11:51 AM, Tomi Valkeinen
> > wrote:
> > > Here are OMAP display subsystem patches for 2.6.39 merge window. Quite a
> > > bit of them, and many changes also in arch/arm/mach-o
Hi All,
> Hello All,
>
> Any comments on this patch?
>
> Regards,
> Keerthy
>
> On Wed, Mar 2, 2011 at 2:17 AM, Keerthy wrote:
> > twl4030_wdt driver and omap_wdt driver are registering as misc_device name
> > as
> > "watchdog" and the same minor number WATCHDOG_MINOR( value = 130).
> > There
On Mon, Mar 28, 2011 at 09:01:29AM +0300, Tomi Valkeinen wrote:
> On Sun, 2011-03-27 at 04:39 +0200, Sebastian Reichel wrote:
> > Hi,
> >
> > I've got problems getting a working tty with the mainline 2.6.38
> > kernel on my Nokia N900. Here is the related output from dmesg:
> >
> > $ grep -E "(om
* Santosh Shilimkar [110328 02:21]:
> --- a/arch/arm/mach-omap2/pm-debug.c
> +++ b/arch/arm/mach-omap2/pm-debug.c
> @@ -40,6 +41,11 @@ static int omap4_pm_suspend(void)
> int state, ret = 0;
> u32 cpu_id = smp_processor_id();
>
> + /* Wakeup timer from suspend */
> + if (wake
* Santosh Shilimkar [110328 02:20]:
> OMAP L2X0 and GIC initialisation code uses BUG_ON() for the
> ioremap() failure scenarios.
>
> Use WARN_ON() instead and allow graceful function exits.
>
> This was suggsted by Kevin Hilman during
> OMAP4 PM code review.
>
> Signed-off-by: Santosh Shilimka
* Santosh Shilimkar [110328 02:20]:
> --- a/arch/arm/mach-omap2/omap4-common.c
> +++ b/arch/arm/mach-omap2/omap4-common.c
> @@ -21,6 +21,7 @@
>
> #include
> #include
> +#include
>
> #ifdef CONFIG_CACHE_L2X0
> void __iomem *l2cache_base;
> @@ -41,6 +42,8 @@ void __init gic_init_irq(void)
On Monday, March 28, 2011, Ben Dooks wrote:
> On Mon, Mar 28, 2011 at 01:29:49AM +0200, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Replace sysdev classes and struct sys_device objects used for "core"
> > power management by Samsung platforms with struct syscore_ops objects
> > t
Hi Rajendra,
On Mon, 21 Mar 2011, Rajendra Nayak wrote:
> On 3/11/2011 10:17 PM, Kevin Hilman wrote:
> > Rajendra Nayak writes:
> >
> > [...]
> >
> > > >
> > > > It's also breaking boot on OMAP35xx BeagleBoard rev C2. The kernel
> > > > boot messages are below - omap2plus_defconfig + DEBUG_L
Vishwa, Shweta,
Vishwanath Sripathy writes:
[...]
>> I am testing Smartreflex on your Branch 'pm-wip/voltdm'. There seems
>> an issue with reading VP registers.
>> For OMAP3 and OMAP4 reading debugfs entries shows constant voltage.
Thanks for testing.
[...]
> I did a quick debug on this and
"Rafael J. Wysocki" writes:
> From: Rafael J. Wysocki
>
> Replace the sysdev class and struct sys_device used for power
> management in the OMAP's GPIO code with a struct syscore_ops object
> which is simpler.
>
> Signed-off-by: Rafael J. Wysocki
Acked-by: Kevin Hilman
Looks fine to me. We'
On Mon, 2011-03-28 at 08:56 -0700, Kevin Hilman wrote:
[...]
> > 1) OMAP4-PM series:
> > git://dev.omapzoom.org/pub/scm/santosh/kernel-omap4-base.git
> > omap4_pm_pmcore_v3
>
> Also, can you post this version of the series to the list,
> w/linux-arm-kernel Cc'd.
Oops, sorry. I see it's already
> -Original Message-
> From: Kevin Hilman [mailto:khil...@ti.com]
> Sent: Monday, March 28, 2011 9:27 PM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; Rajendra Nayak; linux-arm-
> ker...@lists.infradead.org
> Subject: Re: [PATCH v2 00/19] OMAP4: PM: Suspend, CPU-hotplug and
> CP
Hi Santosh,
Santosh Shilimkar writes:
[...]
> Have created two branches as you suggested against latest
> pm-core.
Thanks!
> 1) OMAP4-PM series:
> git://dev.omapzoom.org/pub/scm/santosh/kernel-omap4-base.git
> omap4_pm_pmcore_v3
Also, can you post this version of the series to the list,
w/li
Hi,
On Mon, Mar 28, 2011 at 12:38 AM, Santosh Shilimkar
wrote:
>> If an error occurs in the L3 on any other initiator than MPU,
>> the interrupt goes unhandled given that the 'base' register
>> was calculated with the initialized err_base value (which
>> coincidentally points to MPU) and not with
On Mon, 28 Mar 2011 11:37:22 +0300, Felipe Balbi wrote:
> Hi,
>
> On Sat, Mar 26, 2011 at 07:42:34PM -0400, Ben Gamari wrote:
> > Today I've had a very frustrating time trying to bring up a BeagleBoard
> > (arch/arm/mach-omap2/board-omap2beagle.c) with the 2.6.38
>
> there's no board-omap2beagle
On Mon, 28 Mar 2011 11:34:51 +0300, Felipe Balbi wrote:
> Hi,
>
> On Sat, Mar 26, 2011 at 06:59:18PM -0400, Ben Gamari wrote:
> > Today I've been trying to work through the mess that is musb bring-up on
> > recent kernels (v2.6.38). While I still haven't succeeded in getting a
>
> patches are we
Enable runtime pm and use pm_runtime_get_sync and pm_runtime_put_autosuspend
for OMAP DMA driver.
The DMA driver uses auto suspend feature of runtime pm framework through
which the clock gets disabled automatically if there is no activity for
more than one second.
Testing:
Compile: omap1_defconfi
The current DMA context restore clears all the DMA channel registers
even if the channels are in use. This will result in transfer failures
if repeated DMA transfers are initiated with one time DMA channel
configuration.
Also, remove access to sysconfig register during context save/restore
since i
Certain errata in OMAP2+ processors will require forcing
master standby to "no standby" mode before completing on going
operation. Without this, the results will be unpredictable.
Since current implementation of PM run time framework does not support
changing sysconfig settings during middle of th
If two DMA users tries to set no mstandby mode at the same time, a race
condition would arise. Prevent that by using a spin lock and counting
up/down the number of times nostandby is set/reset.
Initial patch is created by Adrian Hunter
https://patchwork.kernel.org/patch/366831/
Patch reworked to
Patch series to support mstandby mode handling and enabling runtime PM
support for DMA driver.
Change History:
v4:
Fixed Paul's comment:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg47359.html
v3:
Warning fix:
http://thread.gmane.org/gmane.linux.ports.arm.omap/54753/focus=55097
v2:
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Gulati, Shweta
> Sent: Monday, March 28, 2011 4:23 PM
> To: linux-omap@vger.kernel.org; Kevin Hilman
> Subject: Smartreflex on 'pm-wip/voltdm' Branch
>
> Kevin,
>
> I am t
On Fri, Mar 25, 2011 at 4:23 PM, Nicolas Pitre wrote:
> On Fri, 25 Mar 2011, Jason Kridner wrote:
>
>> I very much like this approach. I believed the ability to use the die
>> ID to get a unique code was reasonable approach and that is why I
>> didn't get an EEPROM put onto the BeagleBoard, thoug
Hello All,
Any comments on this patch?
Regards,
Keerthy
On Wed, Mar 2, 2011 at 2:17 AM, Keerthy wrote:
> twl4030_wdt driver and omap_wdt driver are registering as misc_device name as
> "watchdog" and the same minor number WATCHDOG_MINOR( value = 130).
> There is a conflict since the name and mi
Kevin,
> -Original Message-
> From: Kevin Hilman [mailto:khil...@ti.com]
> Sent: Friday, March 25, 2011 8:54 PM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; Rajendra Nayak; linux-arm-
> ker...@lists.infradead.org
> Subject: Re: [PATCH v2 00/19] OMAP4: PM: Suspend, CPU-hotplug
Kevin,
I am testing Smartreflex on your Branch 'pm-wip/voltdm'. There seems
an issue with reading VP registers.
For OMAP3 and OMAP4 reading debugfs entries shows constant voltage.
Logs are:
OMAP3:
# cat /debug/voltage/vdd_mpu_iva/curr_nominal_volt
120
# cat /debug/voltage/vdd_core/curr_nomina
Kevin
> -Original Message-
> From: Kevin Hilman [mailto:khil...@ti.com]
> Sent: Friday, March 25, 2011 8:54 PM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; Rajendra Nayak; linux-arm-
> ker...@lists.infradead.org
> Subject: Re: [PATCH v2 00/19] OMAP4: PM: Suspend, CPU-hotplug a
Hi,
> -Original Message-
> From: ext Sergei Shtylyov [mailto:sshtyl...@mvista.com]
> Sent: 28. maaliskuuta 2011 11:18
> To: Jokiniemi Kalle (Nokia-MS/Tampere)
> Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org; ba...@ti.com;
> Krogerus Heikki (Nokia-MS/Helsinki); jhnik...@gm
Hi,
> -Original Message-
> From: ext Sergei Shtylyov [mailto:sshtyl...@mvista.com]
> Sent: 28. maaliskuuta 2011 11:20
> To: Jokiniemi Kalle (Nokia-MS/Tampere)
> Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org; ba...@ti.com;
> Krogerus Heikki (Nokia-MS/Helsinki); jhnik...@gm
Hello,
> -Original Message-
> From: Heikki Krogerus [mailto:heikki.kroge...@nokia.com]
> Sent: 28. maaliskuuta 2011 12:13
> To: Jokiniemi Kalle (Nokia-MS/Tampere)
> Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org; ba...@ti.com;
> jhnik...@gmail.com; khil...@ti.com
> Subjec
This patch adds configurable wakeup timer support in suspend. Also
for statistics pm counter support is added.
Signed-off-by: Santosh Shilimkar
Cc: Kevin Hilman
---
arch/arm/mach-omap2/omap4-mpuss-lowpower.c |4
arch/arm/mach-omap2/pm-debug.c | 11 +--
arch/arm/ma
CPU local timer(TWD) stops when the CPU is transitioning into
deeper C-States. Since these timers are not wakeup capable, we
need the wakeup capable global timer to program the wakeup time
depending on the next timer expiry.
It can be handled by registering a global wakeup capable timer along
with
With OMAP4 suspend, idle and hotplug series, we no longer need
do_wfi() macro.
Remove the same.
Signed-off-by: Santosh Shilimkar
Cc: Kevin Hilman
---
arch/arm/mach-omap2/include/mach/omap4-common.h | 10 --
1 files changed, 0 insertions(+), 10 deletions(-)
diff --git a/arch/arm/mach
On OMAP4 CPUidle, the low power states are triggered when CPU1
is offlined to OFF power state. When the CPU1 is online, no
low power states are supported.
The patch adds CPU hotplug notifier to manage the C-state
states using CPUidle prepare() hook and CPUIDLE_FLAG_IGNORE
c-state flag.
This was s
On OMAP4430 ES1.0, Power Management features are not supported.
Avoid omap4_pm_init() on ES1.0 silicon so that we can continue
to use same kernel binary to boot on all OMAP4 silicons.
The ES1.0 boot failure with OMAP4 PM series was because of
the clockdomain initialisation code. Hardware supervise
This patch adds MPUSS(MPU Sub System) RET and OFF mode support
to suspend path. For both MPUSS RET and OFF support, CPUs are
programmed to OFF state.
Only MPUSS RET and OFF supported at this point of time. CORE RET
will be added subsequently.
Signed-off-by: Santosh Shilimkar
Cc: Kevin Hilman
--
This patch adds MPUSS low power states in cpuidle.
C1 - CPU0 ON + CPU1 ON + MPU ON
C2 - CPU0 ON + CPU1 OFF + MPU ON
C3 - CPU0 OFF + CPU1 OFF + MPU CSWR
C4 - CPU0 OFF + CPU1 OFF + MPU OFF
MPU OSWR isn't supported yet. To support OSWR, power domain context
registers
When MPUSS hits off-mode e, L2 cache is lost. This patch adds L2X0
necessary maintenance operations and context restoration in the
low power code.
Signed-off-by: Santosh Shilimkar
Cc: Kevin Hilman
---
arch/arm/mach-omap2/omap4-mpuss-lowpower.c | 18
arch/arm/mach-omap2/omap4-sar-layo
This patch adds the CPU0 and CPU1 off mode support. CPUX close switch
retention (CSWR) is not supported by hardware design.
The CPUx OFF mode isn't supported on OMAP4430 ES1.0
CPUx sleep code is common for hotplug, suspend and CPUilde.
Signed-off-by: Santosh Shilimkar
Cc: Kevin Hilman
---
arc
The power management code needs to have access to enable/disable the
gic cpu interface and distributor based on targetted low power
states.
These APIs are suppose to me moved to common ARM GIC library and patch
for the same was posted earlier. The GIC code refactoring is ongoing
and hence for time
From: Rajendra Nayak
The patch adds a basic CPUidle driver for OMAP4. Just
one C state is registered for CPU0 which does a WFI.
CPU1 is left with defualt idle and the low power state
for it is managed via cpu-hotplug.
Signed-off-by: Rajendra Nayak
Signed-off-by: Santosh Shilimkar
Cc: Kevin Hil
On OMAP4 when attempting MPU off-mode or OSWR, the GIC context is
lost. This patch adds GIC context save and restore support.
The context save is done by software and restore is done by
ROM code from predefined SAR locations where the context supposed
to be saved. Refer to OMAP4430 TRM for the SAR
V3 updates:
It's same as V2 with couple of minor updates and its rebased on Kevin's
latest pm-core branch.
- Dropped 'enable_off_mode' flag altogether for OMAP4 as discussed on the list.
- Removed non-supported pm debug entries
The following changes since commit 61cbb3172176b84c106bf0f4c32317c4729
Program non-boot CPUs to hit lowest supported power state
when it is off-lined using cpu hotplug framework.
Signed-off-by: Santosh Shilimkar
Cc: Kevin Hilman
---
arch/arm/mach-omap2/omap-hotplug.c | 18 +-
1 files changed, 13 insertions(+), 5 deletions(-)
diff --git a/arch/ar
As per OMAP4430 TRM, the dynamic dependency between MPUSS<->MEMIF
and MPUSS<->L3_MAIN_1 clockdomains is enable by default. Refer
register CM_MPU_DYNAMICDEP description for details.
But it doesn't seems to work as expected and MPUSS doesn't wakeup
from off-mode if the static dependency is not set b
OMAP L2X0 and GIC initialisation code uses BUG_ON() for the
ioremap() failure scenarios.
Use WARN_ON() instead and allow graceful function exits.
This was suggsted by Kevin Hilman during
OMAP4 PM code review.
Signed-off-by: Santosh Shilimkar
Cc: Kevin Hilman
---
arch/arm/mach-omap2/omap4-com
This patch adds OMAP WakeupGen support. The WakeupGen unit is responsible
for generating wakeup event from the incoming interrupts and enable bits.
The WakeupGen is implemented in MPU Always-On power domain. During normal
operation, WakeupGen delivers external interrupts directly to the GIC.
When t
This patch adds SAR RAM support on OMAP4430. SAR RAM used to save
and restore the HW context in low power modes.
Signed-off-by: Santosh Shilimkar
Cc: Kevin Hilman
---
arch/arm/mach-omap2/include/mach/omap4-common.h |1 +
arch/arm/mach-omap2/omap4-common.c | 31 +++
WakeupGen IP is integrated along with GIC to manage the
interrupt wakeups from CPU low power states. It's located in
always ON power domain. It manages masking/unmasking of
Shared peripheral interrupts(SPI).So the interrupt enable/disable
control should be in sync and consistent at WakeupGen and GI
1 - 100 of 118 matches
Mail list logo