On Thu, 10 Jul 2008, Ivo van Doorn wrote: > > Do you want me to mark rfkill_force_state() as mandatory in the docs? It > > *IS* the preferred way to deal with firmware/hardware-initiated state > > changes, after all. > > Please do. Thanks. > > > The rfkill subsystem will limp along without it, even when there are > > hardware rfkill lines... but no OSD function will work, as the system will > > pick up the change only when someone reads or writes to the state > > attribute... > > That reason alone is good enough for me to mark it mandatory for any drivers > which features the rfkill key. :) Input drivers don't need it at all, so it is not the drivers with rfkill keys (input devices) that need it. Rather, the drivers of wireless devices with hardware rfkill lines are the ones who "need" it. Yeah, I am definately adding it to the docs. Did some locking fixes and other dangerous crap too (in the sense that it can easily force me to down a brown paperbag!), that needs to go to the list for RFC. Will send what I have done already after some light testing. -- "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-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
