Zaurus suspend saga
From: Pavel Machek
Date: Sun Sep 06 2009 - 01:27:30 EST
Even with mtd regression fixed, spitz will still not suspend/resume
I got hint that SPI suspend may be responsible...
with corgi_enter_suspend stubbed out and parts of spitz_should_wakeup
disabled, it suspends/resumes ok.
spitz_pm.c parts -- yes it controls wakeup, but it only seems to read GPIOs?
spitz_should_wakeup: printks do not signal this triggers, perhaps
change is not strictly neccessary.
sharpsl_fatal_check seems to trigger, sending machine to sleep :-(.
fatal reads invalid values -- -108 -- probably because spi is not ready?
is spi suspend/resume required? yes.; and yes spi is resumed too late
in the sequence. Or perhaps fatal battery check is way too early.
Could someone confirm that simply removing sharpsl_fatal_check() fixes
zaurus suspend on 2.6.31?
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/