diff options
| author | Andy Green <andy@openmoko.com> | 2008-11-19 17:09:47 +0000 |
|---|---|---|
| committer | Andy Green <agreen@pads.home.warmcat.com> | 2008-11-19 17:09:47 +0000 |
| commit | 11c78492dc87877aaf1220b6b855e4a9363ca932 (patch) | |
| tree | 5ea1eae6f5e568ac339a712a55b29b743b837ab7 /include | |
| parent | f8d84454949a5669abccf0b9c524f46380050c7f (diff) | |
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>
Diffstat (limited to 'include')
| -rw-r--r-- | include/linux/pcf50633.h | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/include/linux/pcf50633.h b/include/linux/pcf50633.h index 8a75b28606f..0522d922fcc 100644 --- a/include/linux/pcf50633.h +++ b/include/linux/pcf50633.h @@ -129,6 +129,11 @@ extern void pcf50633_register_resume_dependency(struct pcf50633_data *pcf, struct resume_dependency *dep); +/* 0 = initialized and resumed and ready to roll, !=0 = either not + * initialized or not resumed yet + */ +extern int +pcf50633_ready(struct pcf50633_data *pcf); #define PCF50633_FEAT_EXTON 0x00000001 /* not yet supported */ #define PCF50633_FEAT_MBC 0x00000002 |