1. 15 May, 2018 5 commits
    • Taketo Kabe's avatar
      b43: fix transmit failure when VT is switched · 66cffd6d
      Taketo Kabe authored
      Setup:
      Using BCM4306 rev.03 chip based CardBus wireless card.
      IRQ is shared with yenta (cardbus bridge) and i915 (display) driver.
      For firmware, installed latest but dated openfwwf 5.2
      (http://netweb.ing.unibs.it/~openfwwf/)
      
      How-to-reproduce:
      Do "ssh <NetBSD-remotehost>", then "ls -lR /" to generate traffic, then
      repeatedly switch VTs by Alt-F1<>Alt-F2.
      Eventually (within a minute) the card stops working.
      You can receive traffic but no transmission.
      For unknown reason it doesn't occur when just generating traffic by
      "ssh <remotehost> ls -lR /".
      
      With CONFIG_B43_DEBUG=y kernel config, when it stops,
      the debug message shows
          kernel: b43-phy1 debug: Out of order TX status report on DMA ring 1. Expected 148, but got 180
      The slot offset I observed so far was always 32.
      
      When err_out2 is not set to make error messages successive,
      the debug output will be like this:
      kernel: b43-phy1 debug: Out of order TX status report on DMA ring 1. Expected 116, but got 148
      kernel: b43-phy1 debug: Out of order TX status report on DMA ring 1. Expected 116, but got 150
      kernel: b43-phy1 debug: Out of order TX status report on DMA ring 1. Expected 116, but got 120
      kernel: b43-phy1 debug: Out of order TX status report on DMA ring 1. Expected 116, but got 152
      kernel: b43-phy1 debug: Out of order TX status report on DMA ring 1. Expected 116, but got 122
      kernel: b43-phy1 debug: Out of order TX status report on DMA ring 1. Expected 116, but got 154
      kernel: b43-phy1 debug: Out of order TX status report on DMA ring 1. Expected 116, but got 124
      kernel: b43-phy1 debug: Out of order TX status report on DMA ring 1. Expected 116, but got 156
      kernel: b43-phy1 debug: Out of order TX status report on DMA ring 1. Expected 116, but got 126
      The TX ring alternates between 2 sequences; the ring seems
      to be completely confused. Controller restart is needed.
      
      Workaround(1):
      This problem doesn't occur when using propriatory firmware
      you will extract by b43-fwcutter, so it may be a bug in
      openfwwf firmware, as the comment in the b43_dma_handle_txstatus() suggests.
      I wasn't able to find a bug in the terse openfwwf code though.
      
      Workaround(2):
      Using "pio=1" option to not use DMA makes this problem to
      not occur.
      
      Description of the patch:
      This patch will forcibly reset the controller to make it
      work again. Very kludgy and doesn't look right, but
      the traffic will continue to flow.
      Signed-off-by: default avatarTaketo Kabe <kabe@sra-tohoku.co.jp>
      Reviewed-by: default avatarMichael Buesch <m@bues.ch>
      Signed-off-by: default avatarKalle Valo <kvalo@codeaurora.org>
      66cffd6d
    • Siva Rebbagondla's avatar
      rsi: Set wowlan flag while writing wowlan config parameters · 1d18c558
      Siva Rebbagondla authored
      As wowlan enable flag did not set, while writing wowlan parameters to
      card using rsi_send_vap_dynamic_update, which results firmware is unable to
      set wowlan configurations. Hence, setting wowlan flag before sending
      parameters.
      Signed-off-by: default avatarSiva Rebbagondla <siva.rebbagondla@redpinesignals.com>
      Signed-off-by: default avatarSushant Kumar Mishra <sushant.mishra@redpinesignals.com>
      Signed-off-by: default avatarKalle Valo <kvalo@codeaurora.org>
      1d18c558
    • Siva Rebbagondla's avatar
      rsi: reset hibernate_resume flag to work hibernate resume in coex mode. · d76f8513
      Siva Rebbagondla authored
      In coex mode, observed hibernate resume is not working properly, as the
      hibernate_resume flag is not getting reset in rsi_coex_recv_pkt(),
      when common card ready indication received from firmware. Hence resetting
      hibernate_resume flag in this function.
      Signed-off-by: default avatarSiva Rebbagondla <siva.rebbagondla@redpinesignals.com>
      Signed-off-by: default avatarSushant Kumar Mishra <sushant.mishra@redpinesignals.com>
      Signed-off-by: default avatarKalle Valo <kvalo@codeaurora.org>
      d76f8513
    • Sanjay Kumar Konduri's avatar
      rsi: Add null check for virtual interfaces in wowlan config · 54b51720
      Sanjay Kumar Konduri authored
      When the "poweroff" command is executed after wowlan enabled, we have
      observed a system crash. In the system "poweroff" sequence, network-manager
      is sent to inactive state by cleaning up the network interfaces, using
      rsi_mac80211_remove_interface() and when driver tries to access those
      network interfaces in rsi_wowlan_config() which was invoked by SDIO
      shutdown, results in a crash. Added a NULL check before accessing the
      network interfaces in rsi_wowlan_config().
      Signed-off-by: default avatarSanjay Kumar Konduri <sanjay.konduri@redpinesignals.com>
      Signed-off-by: default avatarSiva Rebbagondla <siva.rebbagondla@redpinesignals.com>
      Signed-off-by: default avatarSushant Kumar Mishra <sushant.mishra@redpinesignals.com>
      Signed-off-by: default avatarKalle Valo <kvalo@codeaurora.org>
      54b51720
    • Rafał Miłecki's avatar
      brcmfmac: set WIPHY_FLAG_HAVE_AP_SME flag · 1204aa17
      Rafał Miłecki authored
      brcmfmac is a FullMAC driver and it implements/uses cfg80211 interface
      for stations management. At the same time it doesn't receive or pass up
      management frames.
      
      This flag indicates that authenticator doesn't have to subscribe to or
      handle management frames. Some authenticators (e.g. hostapd) were
      working with brcmfmac thanks to some extra assumptions. This commit
      clears up the situation.
      Signed-off-by: default avatarRafał Miłecki <rafal@milecki.pl>
      Acked-by: default avatarArend van Spriel <arend.vanspriel@broadcom.com>
      Signed-off-by: default avatarKalle Valo <kvalo@codeaurora.org>
      1204aa17
  2. 12 May, 2018 3 commits
  3. 09 May, 2018 4 commits
  4. 04 May, 2018 6 commits
  5. 30 Apr, 2018 22 commits