diff options
| author | Paul Walmsley <paul@pwsan.com> | 2013-02-06 13:48:56 -0700 |
|---|---|---|
| committer | Paul Walmsley <paul@pwsan.com> | 2013-02-06 13:48:56 -0700 |
| commit | 814a18a5d026464f56b3616704b985f9942b29a6 (patch) | |
| tree | c5763da4922f25e2945512d18bced9647cd44d08 /arch/arm/mach-omap2/omap4-common.c | |
| parent | 1e3d8fe771881de323396aaa1efd20243fa974cb (diff) | |
| download | blackbird-op-linux-814a18a5d026464f56b3616704b985f9942b29a6.tar.gz blackbird-op-linux-814a18a5d026464f56b3616704b985f9942b29a6.zip | |
ARM: OMAP AM3517/05: hwmod data: block WFI when EMAC active
According to Mark Greer, on OMAP AM3517/3505 chips, the EMAC is unable
to wake the ARM up from WFI:
http://www.spinics.net/lists/arm-kernel/msg174734.html
Further troubleshooting was unable to narrow the problem down. So we
don't have much choice other than to block WFI when the EMAC is active
with the HWMOD_BLOCK_WFI flag.
Based on Mark's original patch. We're removing the omap_device-based
pm_lats code, so a different approach was needed.
This third version contains some corrections thanks to Mark's review.
Signed-off-by: Paul Walmsley <paul@pwsan.com>
Cc: Mark A. Greer <mgreer@animalcreek.com>
Acked-by: Mark A. Greer <mgreer@animalcreek.com>
Diffstat (limited to 'arch/arm/mach-omap2/omap4-common.c')
0 files changed, 0 insertions, 0 deletions
