State of upstreaming?
Martin Jansa
martin.jansa at gmail.com
Wed Sep 22 09:21:06 CEST 2010
On Wed, Sep 22, 2010 at 09:11:05AM +0200, Radek Polak wrote:
> On Tuesday 21 September 2010 21:08:31 Timo Juhani Lindfors wrote:
>
> > That is interesting news. Can you point me to the config file and git
> > hash that you are using so that I can start testing this version too?
>
> http://github.com/radekp/linux-2.6/tree/qtmoko-v27
>
> Config is also supplied as .config in the root. The tree is based on
> git.openmoko.org branch om-gta02-2.6.34. It has cherry-picked patches from SHR
> [1] except glamo-drm because i was unable to boot whith these patches.
>
> > Afaik at least resume reason support for PMU was missing
> > completely. Is this still the case? It is a serious regression for me
> > since I need to differentiate between RTC wake up and power button
> > press.
>
> I have this file:
>
> /sys/devices/platform/s3c2440-i2c/i2c-0/0-0073/resume_reason
Hi,
this is only subreason from FSO point of view
internal const string SYSFS_RESUME_REASON_PATH = "/class/i2c-adapter/i2c-0/0-0073/neo1973-resume.0/resume_reason";
internal const string SYSFS_RESUME_SUBREASON_PATH = "/class/i2c-adapter/i2c-0/0-0073/resume_reason";
see
http://git.freesmartphone.org/?p=cornucopia.git;a=blob;f=fsousaged/src/plugins/lowlevel_openmoko/plugin.vala;h=91152d6df65ec243c101f2822f3c2958ef436c04;hb=HEAD
how it's used
in short:
FSO tries to read SYSFS_RESUME_REASON_PATH first (but it's not available in
2.6.3[24]) and then only if it's EINT09_PMU it reads second file
SYSFS_RESUME_SUBREASON_PATH.
> it reads value 0002000000
which corresponds to
"0002000000", ResumeReason.PowerKey
you can also find ie "0000000200", ResumeReason.LowBattery
but last time I talked with lindi, he showed me more possible values there,
which were also interresting
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa at gmail.com
More information about the openmoko-kernel
mailing list