backlight device, suspend/resume...

Michael 'Mickey' Lauer mickey at
Tue Jul 8 16:25:42 CEST 2008

Am Dienstag 08 Juli 2008 16:10:49 schrieb Andy Green:
> Somebody in the thread at some point said:
> |>> * backlight is ON and:
> |>> # cat bl_power
> |>> 0
> |>>
> |>> this seems reversed logic here. shouldn't 1 == on, 0 == off? the logic
> |>> seems to continue its inversness when u:
> |>
> |> Been ranting about this for years now -- back then kernel developers
> decided
> |> they want to have it that way and now we have to cope with it in
> userland.
> What happens if we reversed this then, anything blow up?

Yes, everything. Please leave it as is.

> We clearly need a "resume reason handler" who operates before backlight
> comes up at least and can fire some kind of event to userspace apps
> blocked until they fire, even decide to go back to suspend afterwards if
> if the app waiting on the event handled it and said it was OK.

I agree. Can we add a sysfs node where we echo a filename into (think hotplug 
handler)? Or would the more modern approach be to send this out via a netlink 
socket and have userland listen there?


More information about the openmoko-kernel mailing list