| commit | ecb5c96f7da9b081efe3c731a0c7b052c2411536 | |
| author | Andy Green <andy@openmoko.com> | |
| Wed, 2 Jul 2008 21:39:17 +0000 (2 22:39 +0100) | ||
| committer | Andy Green <agreen@localhost.localdomain> | |
| Wed, 2 Jul 2008 21:39:17 +0000 (2 22:39 +0100) | ||
| tree | cbb62333ed25d4004a9e31a6eb108823075a74fd | treesnapshot (tar.gz zip) |
| parent | 83636af17dab41d313411543c57984b5834cfcf2 | commitdiff |
fix-glamo-mci-relationship-with-pcf50633-suspend-resume.patch
After protecting pcf50633 read and write primitives against
operation after suspend or before resume (by blowing a
stack_trace()) I saw glamo-mci was trying to use pcf50633
at these bad times on its own suspend and resume. Since that
part was already done via platform callback, I added an
export in pcf50633 that tells you if it is ready or busy,
and used it to defer (resume power on case) or ignore
(suspend power off case, since pcf50633 already did it)
the mci power call.
Signed-off-by: Andy Green <andy@openmoko.com>
After protecting pcf50633 read and write primitives against
operation after suspend or before resume (by blowing a
stack_trace()) I saw glamo-mci was trying to use pcf50633
at these bad times on its own suspend and resume. Since that
part was already done via platform callback, I added an
export in pcf50633 that tells you if it is ready or busy,
and used it to defer (resume power on case) or ignore
(suspend power off case, since pcf50633 already did it)
the mci power call.
Signed-off-by: Andy Green <andy@openmoko.com>
| arch/arm/mach-s3c2440/mach-gta02.c | diffblobblamehistory | |
| drivers/i2c/chips/pcf50633.c | diffblobblamehistory | |
| include/linux/pcf50633.h | diffblobblamehistory |