1. 22 5月, 2015 1 次提交
    • M
      ath10k: add new 4addr related fw_feature · 48f4ca34
      Michal Kazior 提交于
      Some firmware revisions pad 4th hw address in
      Native Wifi Rx decap. This is the case with 10.x
      and it was assumed that this is true for all
      firmware images.
      
      However QCA988X with 999.999.0.636 and QCA61X4
      with WLAN.RM.2.0-00088 don't have the padding.
      Hence add a feature flag indicating that the
      padding isn't present so firmware images can
      advertise it appropriately. This way driver will
      behave as it was before with old firmware blobs
      and doesn't cause any regressions from user
      perspective.
      
      Effectively this patch enables QCA988X with
      999.999.0.636 and QCA61X4 with WLAN.RM.2.0-00088
      to set up client bridging provided user has an
      updated firmware blob.
      Signed-off-by: NMichal Kazior <michal.kazior@tieto.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      48f4ca34
  2. 09 4月, 2015 1 次提交
  3. 02 4月, 2015 1 次提交
  4. 30 3月, 2015 3 次提交
    • M
      ath10k: rework legacy rx rate decoding · 5528e032
      Michal Kazior 提交于
      Instead of using a hacky table and magic values
      use supported band information advertised to
      mac80211.
      
      This may impact performance a little when dealing
      with legacy rx rates depending on system
      architecture. It's probably negligible.
      
      This also fixes a highly theoretical corner case
      when HT/VHT rates weren't reported correctly if
      channel frequency wasn't known.
      Signed-off-by: NMichal Kazior <michal.kazior@tieto.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      5528e032
    • M
      ath10k: unify tx mode and dispatch · d740d8fd
      Michal Kazior 提交于
      There are a few different tx paths depending on
      firmware and frame itself.
      
      Creating a uniform decision will make it possible
      to switch between different txmode easier, both
      for testing and for future features as well.
      Signed-off-by: NMichal Kazior <michal.kazior@tieto.com>
      Signed-off-by: NMarek Puzyniak <marek.puzyniak@tieto.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      d740d8fd
    • R
      ath10k: add ATH10K_FW_IE_HTT_OP_VERSION · 8348db29
      Rajkumar Manoharan 提交于
      Target to host HTT messages are conflicting between 10.x and other
      firmware revisions. By maintaining separate HTT T2H tables for each
      firmware revisions (main, 10x and tlv) similar to WMI abstraction,
      solves the conflicts. Add ATH10K_FW_IE_HTT_OP_VERSION so that the firmware can
      advertise the HTT interface to ath10k.
      
      This fix is needed to get management frames over HTT (ie.
      ATH10K_FW_FEATURE_HAS_WMI_MGMT_TX disabled) working with 10.2.4.48-2 firmware.
      Otherwise there will be unknown htt events and nothing works:
      
      [30087.438343] ath10k_pci 0000:02:00.0: htt event (19) not handled
      [30087.448691] ath10k_pci 0000:02:00.0: htt event (19) not handled
      [30149.032974] ath10k_pci 0000:02:00.0: htt event (19) not handled
      
      If the firmware does not have ATH10K_FW_IE_HTT_OP_VERSION use the main HTT
      interface. That way old firmware images will still work.
      
      Cc: Michal Kazior <michal.kazior@tieto.com>
      Signed-off-by: NRajkumar Manoharan <rmanohar@qti.qualcomm.com>
      Signed-off-by: NKalle Valo <kvalo@qca.qualcomm.com>
      8348db29
  5. 15 2月, 2015 1 次提交
  6. 27 1月, 2015 3 次提交
  7. 13 1月, 2015 1 次提交
  8. 01 12月, 2014 1 次提交
  9. 26 11月, 2014 1 次提交
  10. 20 11月, 2014 7 次提交
  11. 17 11月, 2014 1 次提交
  12. 24 10月, 2014 10 次提交
  13. 08 10月, 2014 2 次提交
  14. 07 10月, 2014 2 次提交
  15. 18 9月, 2014 5 次提交