On Thu, 2012-05-10 at 00:14 +0100, Russell King - ARM Linux wrote:
On Wed, May 09, 2012 at 03:46:02PM -0700, Kevin Hilman wrote:
Tero Kristo t-kri...@ti.com writes:
Hi,
First version for this work. Applies on top of mainline + iochain set +
OMAP4 core retention set. Working tree
Tero Kristo t-kri...@ti.com writes:
Hi,
First version for this work. Applies on top of mainline + iochain set +
OMAP4 core retention set. Working tree available here:
tree: git://gitorious.org/~kristo/omap-pm/omap-pm-work.git
branch: mainline-3.4-omap4-dev-off
FYI... seems your get repo is
On Wed, May 09, 2012 at 03:46:02PM -0700, Kevin Hilman wrote:
Tero Kristo t-kri...@ti.com writes:
Hi,
First version for this work. Applies on top of mainline + iochain set +
OMAP4 core retention set. Working tree available here:
tree:
On Fri, Apr 20, 2012 at 8:37 PM, Tero Kristo t-kri...@ti.com wrote:
On Fri, 2012-04-20 at 20:21 +0530, Datta, Shubhrajyoti wrote:
On Fri, Apr 20, 2012 at 8:13 PM, Tero Kristo t-kri...@ti.com wrote:
On Fri, 2012-04-20 at 06:55 -0700, Kevin Hilman wrote:
Tero Kristo t-kri...@ti.com writes:
Hi,
First version for this work. Applies on top of mainline + iochain set +
OMAP4 core retention set. Working tree available here:
tree: git://gitorious.org/~kristo/omap-pm/omap-pm-work.git
branch: mainline-3.4-omap4-dev-off
Tested on omap4430 EMU blaze + omap4460 GP panda boards.
Some drivers
On Fri, Apr 20, 2012 at 3:03 PM, Tero Kristo t-kri...@ti.com wrote:
Hi,
First version for this work. Applies on top of mainline + iochain set +
OMAP4 core retention set. Working tree available here:
tree: git://gitorious.org/~kristo/omap-pm/omap-pm-work.git
branch: mainline-3.4-omap4-dev-off
On Fri, 2012-04-20 at 17:50 +0530, T Krishnamoorthy, Balaji wrote:
On Fri, Apr 20, 2012 at 3:03 PM, Tero Kristo t-kri...@ti.com wrote:
Hi,
First version for this work. Applies on top of mainline + iochain set +
OMAP4 core retention set. Working tree available here:
tree:
Tero Kristo t-kri...@ti.com writes:
[...]
I tried your branch on gp/emu devices but could not reproduce this issue.
My observation is that while resuming, omap_hsmmc.1 eMMC is
trying to turn on phoenix vaux1 regulator via i2c which fails due
to controller timeout.
Note: eMMC is present only
On Fri, 2012-04-20 at 06:55 -0700, Kevin Hilman wrote:
Tero Kristo t-kri...@ti.com writes:
[...]
I tried your branch on gp/emu devices but could not reproduce this issue.
My observation is that while resuming, omap_hsmmc.1 eMMC is
trying to turn on phoenix vaux1 regulator via i2c which
On Fri, Apr 20, 2012 at 8:13 PM, Tero Kristo t-kri...@ti.com wrote:
On Fri, 2012-04-20 at 06:55 -0700, Kevin Hilman wrote:
Tero Kristo t-kri...@ti.com writes:
[...]
I tried your branch on gp/emu devices but could not reproduce this issue.
My observation is that while resuming,
On Fri, 2012-04-20 at 20:21 +0530, Datta, Shubhrajyoti wrote:
On Fri, Apr 20, 2012 at 8:13 PM, Tero Kristo t-kri...@ti.com wrote:
On Fri, 2012-04-20 at 06:55 -0700, Kevin Hilman wrote:
Tero Kristo t-kri...@ti.com writes:
[...]
I tried your branch on gp/emu devices but could not
11 matches
Mail list logo