ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: The Dark Avenger <darkavenger@fastmail.fm>
To: ath10k@lists.infradead.org
Subject: DFS fails with QCA6174 and QCA9377
Date: Sat, 21 May 2016 16:19:20 +0200	[thread overview]
Message-ID: <57406E68.6010906@fastmail.fm> (raw)

Hello,

I'm currently trying to set-up an AP in the 5 GHz band. I have a QCA6174 
(Killer 1525) and a QCA9377 adapter at hand.

Unfortunately, while both cards work otherwise well, e.g. I can create 
an AP in the 2.4 GHz range, ACS works,  anything requiring DFS fails:
 >hostapd v. 2.5:
-----
wlp4s0: DFS-CAC-START freq=5580 chan=116 sec_chan=1, width=1, seg0=122, 
seg1=0, cac_time=60s
nl80211: Start radar detection (CAC) 5580 MHz (ht_enabled=1, 
vht_enabled=1, bandwidth=80 MHz, cf1=5610 MHz, cf2=0 MHz)
nl80211: Failed to start radar detection: -16 (Device or resource busy)
DFS start_dfs_cac() failed, -1
-----
Needless to say that the same thing happens on other channel, too, and 
that there're no channels requiring no DFS.
iw list
-----
...
* 5240 MHz [48] (20.0 dBm) (no IR)
* 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
                           DFS state: usable (for 607 sec)
                           DFS CAC time: 60000 ms
                       ...
* 5700 MHz [140] (26.0 dBm) (no IR, radar detection)
                           DFS state: usable (for 607 sec)
                           DFS CAC time: 60000 ms
* 5720 MHz [144] (disabled)
...
------
I compiled kernel 4.5.3 with DFS support, as seems to be confirmed by 
dmesg (see dfs 1):
-----
[    6.020482] ath10k_pci 0000:04:00.0: firmware: direct-loading 
firmware ath10k/QCA6174/hw2.1/firmware-5.bin
[    6.020500] ath10k_pci 0000:04:00.0: qca6174 hw2.1 target 0x05010000 
chip_id 0x003405ff sub 1a56:1525
[    6.020505] ath10k_pci 0000:04:00.0: kconfig debug 0 debugfs 0 
tracing 0 dfs 1 testmode 0
[    6.021159] ath10k_pci 0000:04:00.0: firmware ver 
SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features ignore-otp,no-4addr-pad 
crc32 10bf8e08
[    6.128659] ath10k_pci 0000:04:00.0: firmware: direct-loading 
firmware ath10k/QCA6174/hw2.1/board-2.bin
[    6.129021] ath10k_pci 0000:04:00.0: board_file api 2 bmi_id N/A 
crc32 ae2e275a
[    7.331373] ath10k_pci 0000:04:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 
cal otp max-sta 32 raw 0 hwcrypto 1
-----
For completeness iw get reg
-----
country DE: DFS-ETSI
         (2400 - 2483 @ 40), (N/A, 20), (N/A)
         (5150 - 5250 @ 80), (N/A, 20), (N/A), NO-OUTDOOR
         (5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS
         (5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
         (57000 - 66000 @ 2160), (N/A, 40), (N/A)
-----
The only thing that worries me is that "iw list" does not report any 
"radar detect widths".|.
|So, I am somewhat clueless where the problem lies.  Is it driver, 
firmware, or something else?

Thanks

Roland

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

             reply	other threads:[~2016-05-21 14:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-21 14:19 The Dark Avenger [this message]
2016-05-23  5:10 ` DFS fails with QCA6174 and QCA9377 Michal Kazior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57406E68.6010906@fastmail.fm \
    --to=darkavenger@fastmail.fm \
    --cc=ath10k@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox