1. 11 6月, 2011 3 次提交
  2. 14 5月, 2011 2 次提交
  3. 07 5月, 2011 1 次提交
    • C
      iwlwifi: support the svtool messages interactions through nl80211 test mode · 4613e72d
      Cindy H. Kao 提交于
      This patch adds the feature to support the test mode operation through
      the generic netlink channel NL80211_CMD_TESTMODE between intel
      wireless device iwlwifi and the user space application svtool.
      
      The main purpose is to create a transportation layer between the iwlwifi
      device and the user space application so that the interaction between the
      user space application svtool and the iwlwifi device in the kernel space is
      in a way of generic netlink messaging.
      
      The detail specific functions are:
      
      1. The function iwl_testmode_cmd() is added to digest the svtool test command
         from the user space application. The svtool test commands are categorized  to
         three types : commands to be processed by the device ucode, commands to access
         the registers, and commands to be processed at the driver level(such as reload
         the ucode). iwl_testmode_cmd() dispatches the commands the corresponding handlers
         and reply to user space regarding the command execution status. Extra data is
         returned to the user space application if there's any.
      
      2. The function iwl_testmode_ucode_rx_pkt() is added to multicast all the spontaneous
         messages from the iwlwifi device to the user space. Regardless the message types,
         whenever there is a valid spontaneous message received by the iwlwifi ISR,
         iwl_testmode_ucode_rx_pkt() is invoked to multicast the message content to user
         space. The message content is not attacked and the message parsing is left to
         the user space application.
      
      Implementation guidelines:
      
      1. The generic netlink messaging for iwliwif test mode is through  NL80211_CMD_TESTMODE
         channel, therefore, the codes need to follow the regulations set by cfg80211.ko
         to get the actual device instance ieee80211_ops via cfg80211.ko, so that the iwlwifi
         device is indicated with ieee80211_ops and can be actually accessed.
      
         Therefore, a callback iwl_testmode_cmd() is added to the structure
         iwlagn_hw_ops in iwl-agn.c.
      
      2. It intends to utilize those low level device access APIs from iwlwifi device driver
         (ie. iwlagn.ko) rather than creating it's own set of device access functions.
         For example, iwl_send_cmd(), iwl_read32(), iwl_write8(), and iwl_write32() are reused.
      
      3. The main functions are maintained in new files instead of spreading all over the
         existing iwlwifi driver files.
      
         The new files added are :
      
         drivers/net/wireless/iwlwifi/iwl-sv-open.c
              - to handle the user space test mode application command
                and reply the respective command status to the user space application.
              - to multicast the spontaneous messages from device to user space.
      
         drivers/net/wireless/iwlwifi/iwl-testmode.h
              - the commonly referenced definitions for the TLVs used in
                the generic netlink messages
      Signed-off-by: NCindy H. Kao <cindy.h.kao@intel.com>
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      4613e72d
  4. 23 4月, 2011 2 次提交
  5. 08 4月, 2011 10 次提交
  6. 01 2月, 2011 1 次提交
  7. 03 12月, 2010 1 次提交
  8. 25 11月, 2010 1 次提交
  9. 16 11月, 2010 2 次提交
  10. 08 10月, 2010 2 次提交
  11. 06 10月, 2010 1 次提交
    • W
      iwlagn: reduce redundant parameter definitions · 7cb1b088
      Wey-Yi Guy 提交于
      move paramater definitions to a device paramater structure only
      leaving the device name, which antennas are used and what firmware
      file to use in the iwl_cfg structure.  this will not completely
      remove the redundancies but greatly reduce them for devices that
      only vary by name or antennas.  the parameters that are more
      likely to change within a given device family are left in iwl_cfg.
      also separate bt param structure added to help reduce more.
      Signed-off-by: NJay Sternberg <jay.e.sternberg@intel.com>
      Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      7cb1b088
  12. 04 9月, 2010 1 次提交
    • W
      iwlagn: open/close envlope to force move BT state machine · f7322f8f
      Wey-Yi Guy 提交于
      In uCode, BT state machine need to receive open envlope
      command before perform calibration; followed by close envlope
      command to move to next stage.
      
      Since Linux has two separated uCode, one for init and the second
      one for runtime; we use open envlope commands for init uCode to
      indicate we are ready to perform calibration operation.
      But for runtime uCode, we are not doing any init calibration,
      so we issue open/close envlope commands to force uCode move to
      "BT COEX ON" state.
      Signed-off-by: NWey-Yi Guy <wey-yi.w.guy@intel.com>
      f7322f8f
  13. 27 8月, 2010 2 次提交
  14. 26 8月, 2010 3 次提交
  15. 14 5月, 2010 1 次提交
  16. 11 5月, 2010 2 次提交
  17. 17 4月, 2010 2 次提交
  18. 26 3月, 2010 3 次提交