On Wed, 2008-07-02 at 15:03 +0800, Zhu Yi wrote: > Hi, > > Quote from Documentation/rfkill.txt: > " > The driver should implement the toggle_radio() hook, that: > > ... > > 3. Deactivates the soft rfkill line if none of the hardware rfkill lines > are active and the caller asked for RFKILL_STATE_UNBLOCKED. > " > > It doesn't say what to do if both the hardware and software rfkill lines > are active when RFKILL_STATE_UNBLOCKED is asked. Should we deactivate > the software rfkill in this case? Otherwise below usage won't turn on > the radio: > > hardware rfkill activate > software rfkill activate > RFKILL_STATE_UNBLOCKED request > hardware rfkill deactivate > > Furthermore, if we permit double block, what should get_state() return? > Shouldn't rfkill_state be bitmap instead of enum? That would be more useful than the current enum, yes. Dan -- 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
