1. 17 3月, 2015 3 次提交
  2. 27 2月, 2015 2 次提交
  3. 28 1月, 2015 2 次提交
  4. 07 1月, 2015 4 次提交
  5. 18 11月, 2014 1 次提交
  6. 03 10月, 2014 2 次提交
  7. 01 10月, 2014 1 次提交
  8. 16 9月, 2014 3 次提交
  9. 23 7月, 2014 1 次提交
  10. 19 7月, 2014 1 次提交
  11. 26 6月, 2014 4 次提交
  12. 17 5月, 2014 1 次提交
  13. 23 4月, 2014 2 次提交
  14. 28 3月, 2014 1 次提交
  15. 01 3月, 2014 2 次提交
  16. 16 11月, 2013 1 次提交
  17. 12 11月, 2013 1 次提交
  18. 27 8月, 2013 1 次提交
  19. 27 7月, 2013 2 次提交
  20. 24 7月, 2013 1 次提交
  21. 23 7月, 2013 1 次提交
    • D
      mwifiex: fix IRQ enable/disable · 232fde06
      Daniel Drake 提交于
      During tear down (e.g. mwifiex_sdio_remove during system suspend),
      mwifiex left IRQs enabled for a significant period of time when it was
      unable to handle them correctly. This caused interrupt storms and
      interfered with the bluetooth interface on the same SDIO card.
      
      Solve this by disabling interrupts at the point when they can no longer
      be handled correctly, which is at the start of mwifiex_remove_card().
      
      For cleanliness, we now enable interrupts in the mwifiex_add_card() path,
      to be symmetrical with the disabling of interrupts. We also couple the
      registration of the sdio IRQ handler with the actual enable/disable of
      interrupts at the hardware level.
      
      I also removed a write to this register in mwifiex_init_sdio which seemed
      pointless and won't cause any ill effects now that we only register
      the SDIO IRQ handler when we are ready to accept interrupts.
      
      Includes some corrections from Amitkumar Karwar.
      Signed-off-by: NDaniel Drake <dsd@laptop.org>
      Acked-by: NBing Zhao <bzhao@marvell.com>
      Signed-off-by: NJohn W. Linville <linville@tuxdriver.com>
      232fde06
  22. 23 5月, 2013 3 次提交