All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: ignore radar PHY errors when DFS is not enabled
Date: Fri, 9 Jan 2015 19:57:37 +0100	[thread overview]
Message-ID: <54B024A1.4040809@broadcom.com> (raw)
In-Reply-To: <1420822458-531-1-git-send-email-sw@simonwunderlich.de>

On 01/09/15 17:54, Simon Wunderlich wrote:
> Performing spectral scans on 5 GHz channels may result in PHY errors
> sent by the hardware, even if DFS support is not enabled in the driver
> (e.g. channel scanning or passive monitoring). In that case channels may
> falsely get marked as 'unusable'. To fix that, only process radar PHY
> errors when radar is explicitly enabled in the driver.

Hi Simon,

Not an ath9k expert, but I would think those channels would already be 
marked as unusable, because DFS is disabled in the driver. Or does this 
also affect 5G channels that do not require DFS.

Regards,
Arend

> Cc: Stable<stable@vger.kernel.org>  [v3.10+]
> Reported-by: Mathias Kretschmer<mathias.kretschmer@fokus.fraunhofer.de>
> Signed-off-by: Simon Wunderlich<sw@simonwunderlich.de>
> ---
>   drivers/net/wireless/ath/ath9k/dfs.c | 6 ++++++
>   1 file changed, 6 insertions(+)
>
> diff --git a/drivers/net/wireless/ath/ath9k/dfs.c b/drivers/net/wireless/ath/ath9k/dfs.c
> index 726271c..3d04905 100644
> --- a/drivers/net/wireless/ath/ath9k/dfs.c
> +++ b/drivers/net/wireless/ath/ath9k/dfs.c
> @@ -152,6 +152,12 @@ void ath9k_dfs_process_phyerr(struct ath_softc *sc, void *data,
>   		return;
>   	}
>
> +	if (!sc->hw->conf.radar_enabled) {
> +		ath_dbg(common, DFS,
> +			"Error: received radar phyerr while radar was disabled\n");
> +		return;
> +	}
> +
>   	datalen = rs->rs_datalen;
>   	if (datalen == 0) {
>   		DFS_STAT_INC(sc, datalen_discards);

WARNING: multiple messages have this Message-ID (diff)
From: Arend van Spriel <arend@broadcom.com>
To: Simon Wunderlich <sw@simonwunderlich.de>
Cc: <linux-wireless@vger.kernel.org>, <ath9k-devel@lists.ath9k.org>,
	<kvalo@qca.qualcomm.com>,
	<mathias.kretschmer@fokus.fraunhofer.de>,
	<stable@vger.kernel.org>
Subject: Re: [PATCH] ath9k: ignore radar PHY errors when DFS is not enabled
Date: Fri, 9 Jan 2015 19:57:37 +0100	[thread overview]
Message-ID: <54B024A1.4040809@broadcom.com> (raw)
In-Reply-To: <1420822458-531-1-git-send-email-sw@simonwunderlich.de>

On 01/09/15 17:54, Simon Wunderlich wrote:
> Performing spectral scans on 5 GHz channels may result in PHY errors
> sent by the hardware, even if DFS support is not enabled in the driver
> (e.g. channel scanning or passive monitoring). In that case channels may
> falsely get marked as 'unusable'. To fix that, only process radar PHY
> errors when radar is explicitly enabled in the driver.

Hi Simon,

Not an ath9k expert, but I would think those channels would already be 
marked as unusable, because DFS is disabled in the driver. Or does this 
also affect 5G channels that do not require DFS.

Regards,
Arend

> Cc: Stable<stable@vger.kernel.org>  [v3.10+]
> Reported-by: Mathias Kretschmer<mathias.kretschmer@fokus.fraunhofer.de>
> Signed-off-by: Simon Wunderlich<sw@simonwunderlich.de>
> ---
>   drivers/net/wireless/ath/ath9k/dfs.c | 6 ++++++
>   1 file changed, 6 insertions(+)
>
> diff --git a/drivers/net/wireless/ath/ath9k/dfs.c b/drivers/net/wireless/ath/ath9k/dfs.c
> index 726271c..3d04905 100644
> --- a/drivers/net/wireless/ath/ath9k/dfs.c
> +++ b/drivers/net/wireless/ath/ath9k/dfs.c
> @@ -152,6 +152,12 @@ void ath9k_dfs_process_phyerr(struct ath_softc *sc, void *data,
>   		return;
>   	}
>
> +	if (!sc->hw->conf.radar_enabled) {
> +		ath_dbg(common, DFS,
> +			"Error: received radar phyerr while radar was disabled\n");
> +		return;
> +	}
> +
>   	datalen = rs->rs_datalen;
>   	if (datalen == 0) {
>   		DFS_STAT_INC(sc, datalen_discards);


  reply	other threads:[~2015-01-09 18:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-09 16:54 [ath9k-devel] [PATCH] ath9k: ignore radar PHY errors when DFS is not enabled Simon Wunderlich
2015-01-09 16:54 ` Simon Wunderlich
2015-01-09 18:57 ` Arend van Spriel [this message]
2015-01-09 18:57   ` Arend van Spriel
2015-01-10 16:26   ` [ath9k-devel] " Simon Wunderlich
2015-01-10 16:26     ` Simon Wunderlich
2015-01-13 10:16     ` [ath9k-devel] " Zefir Kurtisi
2015-01-13 10:16       ` Zefir Kurtisi
2015-01-13 11:04       ` [ath9k-devel] " Simon Wunderlich
2015-01-13 11:04         ` Simon Wunderlich
2015-01-13 12:08         ` [ath9k-devel] " Zefir Kurtisi
2015-01-13 12:08           ` Zefir Kurtisi
2015-01-15 14:30         ` [ath9k-devel] " Kalle Valo
2015-01-15 14:30           ` Kalle Valo
2015-01-15 15:58           ` [ath9k-devel] " Simon Wunderlich
2015-01-15 15:58             ` Simon Wunderlich

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=54B024A1.4040809@broadcom.com \
    --to=arend@broadcom.com \
    --cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.