On Wed, 09 Jul 2008, Ivo van Doorn wrote: > It is not mandatory if you are writing rfkill support for a driver that does not > come with a rfkill switch. Such drivers can make use of the rfkill events produced > by the hardware which does have such a switch. > > When the hardware does have the rfkill switch, then yes rfkill_force_state() is mandatory. > The get_state() callback function is optional, and allows rfkill to differentiate > between soft and hardblock. 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. 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... -- "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
