[Bug 80] wakeup reason not in /proc/cmdline

[Joerg Reisenweber]

Am Mo  26. Mai 2008 schrieb bugzilla-daemon at bugzilla.openmoko.org:
> http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=80
> 
> andy at openmoko.com changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|NEW                         |RESOLVED
>          Resolution|                            |FIXED
> 
> 
> 
> ------- Additional Comments From andy at openmoko.com  2008-05-26 11:59 -------
> If you have a U-Boot with uboot-add-find-wake-reason.patch (in git for a 
week
> now) and current git stable branch kernel,
> 
> $ cat /sys/devices/platform/neo1973-resume.0/resume_reason
> 
> gets you a resume reason list like this:
> 
>   EINT00_ACCEL1
>   EINT01_GSM
>   EINT02_BLUETOOTH
>   EINT03_DEBUGBRD
>   EINT04_JACK
>   EINT05_WLAN
>   EINT06_AUXKEY
>   EINT07_HOLDKEY
>   EINT08_ACCEL2
> * EINT09_PMU
>     adpins
>     adprem
>     usbins
>     usbrem
>     rtcalarm
>     second
>     onkeyr
>     onkeyf
>     exton1r
>     exton1f
>     exton2r
>     exton2f
>     exton3r
>     exton3f
>   * batfull
>     chghalt
>     thlimon
>     thlimoff
>     usblimon
>     usblimoff
>     adcrdy
>     onkey1s
>     lowsys
>     lowbat
>     hightmp
>     autopwrfail
>     dwn1pwrfail
>     dwn2pwrfail
>     ledpwrfail
>     ledovp
>     ldo1pwrfail
>     ldo2pwrfail
>     ldo3pwrfail
>     ldo4pwrfail
>     ldo5pwrfail
>     ldo6pwrfail
>     hcidopwrfail
>     hcidoovl
>   EINT10_NULL
>   EINT11_NULL
>   EINT12_GLAMO
>   EINT13_NULL
>   EINT14_NULL
>   EINT15_NULL
> 
> This is suitable for userspace to parse with grep; if drivers are interested 
in
> wake reason, the EINT_* stuff is available as a bitfield in kernelspace and 
the
> PMU-specific reason is as available as a bitfield as soon as I2C and PMU 
resumes
> and services its interrupt.

I think, the textual representation 
in /sys/devices/platform/neo1973-resume.0/resume_reason should be more 
agnostic about particular system architecture. E.g we might see usbins, 
usbrem on a completely different source - like SoC-USB-OTG controller - in 
future designs (GTA0x). EINT04_JACK and EINT07_HOLDKEY may move to Wolfson 
WM8753 internal interrupt sources even for GTA03. I suggest to use completely 
symbolic names like 
EINT04_JACK -> HP-JACKINSERT
usbins -> USB-JACKINSERT
This allows userspace to work independent of actual platform.

Also I wonder whether it's of any meaning to have neo1973 as part of the path, 
where we talk about neoFreerunner actually. Same considerations.

/jOERG
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
Url : http://lists.openmoko.org/pipermail/openmoko-kernel/attachments/20080526/3d525805/attachment.pgp