On Wed, 02 Jul 2008, Johannes Berg wrote: > > (I've written real input drivers before) but rather that nobody really > > knows how userspace/kernel interaction wrt. rfkill should work. > > Oh and there's no need to explain on the mailing list, just make sure > the new rfkill docs are clear wrt. the way forward. Ok. Is what we currently have (i.e. what is in -next/wireless-testing) already enough? Are there any topics I should try to clarify better on Documentation/rfkill.txt ? > Another thing that just occurred to me: it might be nice to have a few > (per-hardware, global?) LED triggers that can be bound to LEDs and that > always reflect the state the driver says the radio has (hw-rfkill) or > the driver is asked to enforce (sw-rfkill) Well, it should be doable with the new rfkill notify chain. The chain is called on every rfkill state change, and it will also get called when global state changes (I am working on exposing the global state to userspace and the rest of the kernel, now. I don't exactly know the best way to go about it, expect an RFC post soon about it). So, one could write a separate module (e.g. rfkill-led) that registers with the notify chain, and feeds the events to as many led triggers as he wants to. That would add LED trigger support to every rfkill driver in one go. You could have different triggers for global states (there is one global state per switch type), as well as triggers for each individual kill switch, the notify chain exports enough data (a pointer to the rfkill structure) for that (and if it doesn't, we ought to fix it so that it will :-) ). Would "rfkill switch registered" and "rfkill switch unregistered" notifications on the rfkill notify chain help write something like a led trigger driver? If so, I will add them. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
