1. 13 Sep, 2014 3 commits
  2. 12 Sep, 2014 7 commits
  3. 11 Sep, 2014 2 commits
    • Sujith Manoharan's avatar
      Revert "ath9k: Calculate sleep duration" · ae0fd635
      Sujith Manoharan authored
      This reverts commit 09ebb810.
      
      ath9k_hw_set_sta_beacon_timers() configures AR_TIM_PERIOD with
      the beacon interval. Before this commit, the sleepduration was
      never greater than the beacon interval. But now, the behavior
      has changed. For example, with an AP that uses a beacon interval of 100:
      
      ath: phy9: next beacon 61128704
      ath: phy9: beacon period 204800
      ath: phy9: DTIM period 204800
      
      If the sleepduration is calculated based on the listen time, then
      the bmiss threshold should also be changed since the HW would
      be in sleep state for a longer time, but that is not done currently.
      
      To avoid configuring a higher beacon interval based on the sleepduration,
      revert to the original behavior. Power consumption is not a
      problem since PS is disabled in ath9k anyway.
      
      Cc: stable@vger.kernel.org
      Cc: Rajkumar Manoharan <rmanohar@qti.qualcomm.com>
      Signed-off-by: default avatarSujith Manoharan <c_manoha@qca.qualcomm.com>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      ae0fd635
    • David Jander's avatar
      can: flexcan: avoid calling usleep_range from interrupt context · 8badd65e
      David Jander authored
      Apparently can_restart() runs from a (timer-) interrupt and can call
      flexcan_chip_[en|dis]able(), so avoid using usleep_range()
      Signed-off-by: default avatarDavid Jander <david@protonic.nl>
      Cc: linux-stable <stable@vger.kernel.org>
      Signed-off-by: default avatarMarc Kleine-Budde <mkl@pengutronix.de>
      8badd65e
  4. 10 Sep, 2014 11 commits
  5. 09 Sep, 2014 2 commits
  6. 08 Sep, 2014 15 commits