Messages in this thread |  | | | Date | Sun, 6 Sep 2009 07:26:53 +0200 | | From | Pavel Machek <> | | Subject | Zaurus suspend saga |
| |
Hi!
Even with mtd regression fixed, spitz will still not suspend/resume correctly.
I got hint that SPI suspend may be responsible...
With 2.6.31-rc7:
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?
Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
|  |