ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@openmesh.com>
To: ath10k@lists.infradead.org
Cc: daniel.bailey@openmesh.com, simon.wunderlich@openmesh.com
Subject: ath10k: 160MHz/80+80 radar detect with Wave2 cards
Date: Thu, 26 Jul 2018 12:45:47 +0200	[thread overview]
Message-ID: <4178610.dnsFcfIAIc@bentobox> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1067 bytes --]

Hi,

as we know, some wave2 cards support 160MHz (with some limitations). This also 
requires support for radar detection with 160MHz/80+80 or otherwise cfg80211 
will reject this setting. I would like to propose following change but I am 
unsure whether it actually works correctly on this hardware (QCA9888).

    diff --git a/drivers/net/wireless/ath/ath10k/mac.c b/drivers/net/wireless/ath/ath10k/mac.c
    index 2bea5e8..3b43759 100644
    --- a/drivers/net/wireless/ath/ath10k/mac.c
    +++ b/drivers/net/wireless/ath/ath10k/mac.c
    @@ -7951,7 +7951,9 @@ static const struct ieee80211_iface_combination ath10k_10_4_if_comb[] = {
     		.radar_detect_widths =	BIT(NL80211_CHAN_WIDTH_20_NOHT) |
     					BIT(NL80211_CHAN_WIDTH_20) |
     					BIT(NL80211_CHAN_WIDTH_40) |
    -					BIT(NL80211_CHAN_WIDTH_80),
    +					BIT(NL80211_CHAN_WIDTH_80) |
    +					BIT(NL80211_CHAN_WIDTH_80P80) |
    +					BIT(NL80211_CHAN_WIDTH_160)
     #endif
     	},
     };

Does anyone know whether radar detection is supported for these channel 
widths?

Kind regards,
	Sven

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

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

                 reply	other threads:[~2018-07-26 10:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4178610.dnsFcfIAIc@bentobox \
    --to=sven.eckelmann@openmesh.com \
    --cc=ath10k@lists.infradead.org \
    --cc=daniel.bailey@openmesh.com \
    --cc=simon.wunderlich@openmesh.com \
    /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