[PATCH 0/5] Power supply and resume ordering meddling

[Andy Green]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
| Michael 'Mickey' Lauer wrote:
|> a) This hardcoded behaviour should be configurable
|> (CONFIG_HARDCODED_CHARGING_LED) for people who rather want userland
to be in
|> control of the LEDs.
|
| Indeed. In fact, this is something that should be handled completely
| in user space, without more kernel involvement than providing a means
| to efficiently determine the charging state and changes to it.

Well as you realized while writing that, "handled completely in
userspace" is not the right answer here, the event-driven tracking of
charger state from the kernel is needed to drive any userspace policy.
~   Which we now have, to "widespread critical acclaim".

What is the proposal for passing the charging on and off events
painfully tracked by the patch to userspace then?  There's a bunch of
ways like power events, APM and I well know that whichever one I pick
and implement, a mob will appear telling me it has to be some other one.

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkhFAiMACgkQOjLpvpq7dMpoBwCfXwIccIxMQ9uAv8+1f+ClqxXS
ifwAn3QnUxY8gsmZEoi+oecYZoJn/Iyf
=XEJe
-----END PGP SIGNATURE-----