ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Sven Eckelmann <sven.eckelmann@openmesh.com>
Cc: Marek Puzyniak <marek.puzyniak@tieto.com>,
	Simon Wunderlich <simon.wunderlich@openmesh.com>,
	ath10k@lists.infradead.org
Subject: Re: [PATCH] ath10k: Prevent active scans on potential unusable channels
Date: Thu, 26 Jul 2018 16:47:00 +0300	[thread overview]
Message-ID: <87r2jqt8h7.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20180710094448.13201-1-sven.eckelmann@openmesh.com> (Sven Eckelmann's message of "Tue, 10 Jul 2018 11:44:48 +0200")

Sven Eckelmann <sven.eckelmann@openmesh.com> writes:

> The QCA4019 hw1.0 firmware 10.4-3.2.1-00050 and 10.4-3.5.3-00053 (and most
> likely all other) seem to ignore the WMI_CHAN_FLAG_DFS flag during the
> scan. This results in transmission (probe requests) on channels which are
> not "available" for transmissions.
>
> Since the firmware is closed source and nothing can be done from our side
> to fix the problem in it, the driver has to work around this problem. The
> WMI_CHAN_FLAG_PASSIVE seems to be interpreted by the firmware to not
> scan actively on a channel unless an AP was detected on it. Simple probe
> requests will then be transmitted by the STA on the channel.
>
> ath10k must therefore also use this flag when it queues a radar channel for
> scanning. This should reduce the chance of an active scan when the channel
> might be "unusable" for transmissions.
>
> Fixes: e8a50f8ba44b ("ath10k: introduce DFS implementation")
> Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com>

You didn't CC linux-wireless so I don't see this in patchwork. Can you
resend, please?

-- 
Kalle Valo

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

  reply	other threads:[~2018-07-26 13:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10  9:44 [PATCH] ath10k: Prevent active scans on potential unusable channels Sven Eckelmann
2018-07-26 13:47 ` Kalle Valo [this message]
2018-07-26 13:59   ` Sven Eckelmann
2018-07-26 14:22     ` Kalle Valo
2018-07-26 14:33       ` Sven Eckelmann

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=87r2jqt8h7.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=marek.puzyniak@tieto.com \
    --cc=simon.wunderlich@openmesh.com \
    --cc=sven.eckelmann@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