Hi,
Andy Green wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Somebody in the thread at some point said:
| - Looking at this I don't understand where is implemented is_enable ops
| function of the regulator.
| So how does it work the regulator_is_enabled function?
Balaji mentioned that when he removed the regulator suspend / resume
handler stuff recently, this went away? Is this tree you're using older
than 3 days?
http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=276709515c384f4239c9479b56fcf008ae37eec8
Ok
| - The rtc_set_time is executed in process context I think, like the
| worker of the pcf50633, how can the
| function prevents a race without a mutex?
I seem to recall the register read and write functions are themselves
protected, what are you thinking it races against?
Right. I look in to the openmoko specific code in the spare time, so
It's a my mistake.
Sorry
| - I think the flicker is an android issue.
That sounds good... does it seem there is a way to impact Android's
behaviour about the flicker then by modifying something in Android?
- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAklmgfwACgkQOjLpvpq7dMpnEQCfVd1bDgaiXn5D2HLhbKXCqjDS
3+8An3yl8951dKmfGEXVx2nk2FIjpskf
=/r97
-----END PGP SIGNATURE-----
Regards Michael
