|
|
Re: [PATCH 00/19] ARM: OMAP4 device off support |
On Fri, Apr 20, 2012 at 8:13 PM, Tero Kristo <t-kristo@xxxxxx> wrote: > On Fri, 2012-04-20 at 06:55 -0700, Kevin Hilman wrote: >> Tero Kristo <t-kristo@xxxxxx> 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 sdp/blaze >> > >> > Did you try this with off-mode enabled and did you check the device >> > actually goes to off? (see pm_debug/count and verify core off count is >> > increasing.) And as said, I was only able to see this problem on a blaze >> > device, panda works fine. But yes, you are probably right and it is not >> > an MMC driver issue but I2C. >> >> Can you try the patch below? It sounds like the same problem. > > Doesn't help with this one. I guess I2C loses context during device off > and it is not restored properly. > > -Tero Could you try the following patch https://lkml.org/lkml/2012/3/30/345 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
[Linux ARM (vger)] [Linux ARM MSM] [Linux Omap] [Linux Arm] [Linux Tegra] [Fedora ARM] [eCos] [Linux Fastboot] [Gcc Help] [Git] [DCCP] [IETF Announce] [Security] [PDAs] [Linux] [Linux MIPS] [Yosemite Campsites] [Photos]
![]() |
![]() |