1. 02 Feb, 2012 6 commits
  2. 30 Jan, 2012 17 commits
  3. 28 Jan, 2012 5 commits
    • Johannes Berg's avatar
      iwlwifi: always restrict scan dwell in P2P · 4c7d2fe9
      Johannes Berg authored
      
      
      Whenever the PAN (P2P) context is active, it
      has timers in the uCode that prevent sleep,
      so scanning can't be out of channel for more
      than the beacon interval programmed into the
      device.
      
      Before this patch, a full scan including any
      passive channels when P2P was active would
      stall forever because it wouldn't find time
      to execute the passive requests (for default
      beacon intervals of 100 TU.)
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: default avatarWey-Yi Guy <wey-yi.w.guy@intel.com>
      4c7d2fe9
    • Wey-Yi Guy's avatar
      iwlwifi: add option to disalbe LED · 42602dd4
      Wey-Yi Guy authored
      
      
      Led has no use for some platform.
      Add additional module parameter option to disable LED
      Signed-off-by: default avatarWey-Yi Guy <wey-yi.w.guy@intel.com>
      42602dd4
    • Johannes Berg's avatar
      iwlwifi: fix uCode event tracing · 98d4bf0c
      Johannes Berg authored
      
      
      Fix multiple bugs in event tracing:
      
      1) If you enable uCode tracing with the device down,
         it will still attempt to access the device and
         continuously log "MAC is in deep sleep!" errors.
         Fix this by only starting logging when the device
         is actually alive.
      
      2) Now you can set the flag when the device is down,
         but logging doesn't happen when you bring it up.
         To fix that, start logging when the device comes
         alive. This means we don't log before -- we could
         do that but I don't need it right now.
      
      3) For some reason we read the error instead of the
         event log -- use the right pointer.
      
      4) Optimise SRAM reading of event log header.
      
      5) Fix reading write pointer == capacity, which can
         happen due to racy SRAM access
      
      6) Most importantly: fix an error where we would try
         to read WAY too many events (like 2^32-300) when
         we read the wrap counter before it is updated by
         the uCode -- this does happen in practice and will
         cause the driver to hang the machine.
      
      7) Finally, change the timer to 10ms instead of 100ms
         as 100ms is too slow to capture all data with a
         normal event log and with 100ms the log will wrap
         multiple times before we have a chance to read it.
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: default avatarWey-Yi Guy <wey-yi.w.guy@intel.com>
      98d4bf0c
    • Wey-Yi Guy's avatar
      iwlwifi: fix typo · de46fb07
      Wey-Yi Guy authored
      
      
      Fix few places of typo
      Signed-off-by: default avatarWey-Yi Guy <wey-yi.w.guy@intel.com>
      de46fb07
    • Wey-Yi Guy's avatar
      Merge branch 'master' of... · 03e369d9
      Wey-Yi Guy authored
      Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next into wireless-next
      03e369d9
  4. 27 Jan, 2012 12 commits