1. 26 Jun, 2008 3 commits
    • Henrique de Moraes Holschuh's avatar
      rfkill: add the WWAN radio type · 477576a0
      Henrique de Moraes Holschuh authored
      
      
      Unfortunately, instead of adding a generic Wireless WAN type, a technology-
      specific type (WiMAX) was added.  That's useless for other WWAN devices,
      such as EDGE, UMTS, X-RTT and other such radios.
      
      Add a WWAN rfkill type for generic wireless WAN devices.  No keys are added
      as most devices really want to use KEY_WLAN for WWAN control (in a cycle of
      none, WLAN, WWAN, WLAN+WWAN) and need no specific keycode added.
      Signed-off-by: default avatarHenrique de Moraes Holschuh <hmh@hmh.eng.br>
      Acked-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Cc: Iñaky Pérez-González <inaky.perez-gonzalez@intel.com>
      Cc: David S. Miller <davem@davemloft.net>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      477576a0
    • Henrique de Moraes Holschuh's avatar
      rfkill: add read-write rfkill switch support · 801e49af
      Henrique de Moraes Holschuh authored
      
      
      Currently, rfkill support for read/write rfkill switches is hacked through
      a round-trip over the input layer and rfkill-input to let a driver sync
      rfkill->state to hardware changes.
      
      This is buggy and sub-optimal.  It causes real problems.  It is best to
      think of the rfkill class as supporting only write-only switches at the
      moment.
      
      In order to implement the read/write functionality properly:
      
      Add a get_state() hook that is called by the class every time it needs to
      fetch the current state of the switch.  Add a call to this hook every time
      the *current* state of the radio plays a role in a decision.
      
      Also add a force_state() method that can be used to forcefully syncronize
      the class' idea of the current state of the switch.  This allows for a
      faster implementation of the read/write functionality, as a driver which
      get events on switch changes can avoid the need for a get_state() hook.
      
      If the get_state() hook is left as NULL, current behaviour is maintained,
      so this change is fully backwards compatible with the current rfkill
      drivers.
      
      For hardware that issues events when the rfkill state changes, leave
      get_state() NULL in the rfkill struct, set the initial state properly
      before registering with the rfkill class, and use the force_state() method
      in the driver to keep the rfkill interface up-to-date.
      
      get_state() can be called by the class from atomic context. It must not
      sleep.
      Signed-off-by: default avatarHenrique de Moraes Holschuh <hmh@hmh.eng.br>
      Acked-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Cc: Dmitry Torokhov <dtor@mail.ru>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      801e49af
    • Henrique de Moraes Holschuh's avatar
      rfkill: clarify meaning of rfkill states · f3146aff
      Henrique de Moraes Holschuh authored
      
      
      rfkill really should have been named rfswitch.  As it is, one can get
      confused whether RFKILL_STATE_ON means the KILL switch is on (and
      therefore, the radio is being *blocked* from operating), or whether it
      means the RADIO rf output is on.
      
      Clearly state that RFKILL_STATE_ON means the radio is *unblocked* from
      operating (i.e. there is no rf killing going on).
      Signed-off-by: default avatarHenrique de Moraes Holschuh <hmh@hmh.eng.br>
      Acked-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
      Cc: Dmitry Torokhov <dtor@mail.ru>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      f3146aff
  2. 31 Jan, 2008 1 commit
  3. 10 Oct, 2007 6 commits
  4. 07 Jun, 2007 1 commit
  5. 07 May, 2007 1 commit