Openmoko Bug #2324: resume_reason can show EINT01_GSM even if GSM is off
Openmoko Public Trac
bugs at docs.openmoko.org
Sun Dec 27 01:54:15 CET 2009
#2324: resume_reason can show EINT01_GSM even if GSM is off
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: normal | Keywords: resume_reason GSM
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Steps to reproduce:
1) receive a call while the phone is in suspend
2) stop GSM
3) suspend the phone
4) press power button
5) check /sys/class/i2c-
adapter/i2c-0/0-0073/neo1973-resume.0/resume_reason for resume reason
Expected results:
5) resume reason is only EINT09_PMU
Actual results:
5) both GSM and PMU are shown as a resume reason:
{{{
EINT00_ACCEL1
* EINT01_GSM
EINT02_BLUETOOTH
EINT03_DEBUGBRD
EINT04_JACK
EINT05_WLAN
EINT06_AUXKEY
EINT07_HOLDKEY
EINT08_ACCEL2
* EINT09_PMU
EINT10_NULL
EINT11_NULL
EINT12_GLAMO
EINT13_NULL
EINT14_NULL
EINT15_NULL
}}}
More info:
1) linux andy-tracking a3587e4ed77974ad
2) Qi 9ef7754b8243457c
3) the problem does not appear unless the GSM has woken the system up at
least once
4) I read some source code and was able to figure out:
4.1) drivers/misc/neo1973_pm_resume_reason.c reads resume reason from
gstatus4 at 0x560000BC
4.2) Qi has written to this address the contents of SRCPND at 0x4A000000
I mmap()'d SRCPND via /dev/mem and it seems to contain the bytes
0c 20 00 00. (I have no idea if simple mmap() is actually able to read
this correctly.)
5) If I execute steps 3 - 5 again GSM is not shown as a resume reason
anymore.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2324>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
More information about the buglog
mailing list