All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alvin Šipraga" <ALSI@bang-olufsen.dk>
To: James Prestwood <prestwoj@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] brcmfmac: include missing AP scan feature
Date: Fri, 25 Feb 2022 22:55:21 +0000	[thread overview]
Message-ID: <87o82ud09z.fsf@bang-olufsen.dk> (raw)
In-Reply-To: <20220224181809.2808754-1-prestwoj@gmail.com> (James Prestwood's message of "Thu, 24 Feb 2022 10:18:09 -0800")

Hi James,

James Prestwood <prestwoj@gmail.com> writes:

> This driver does not advertise this feature yet scanning with on an
> AP interface appears to work just fine.
> ---
>  drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> I've submitted this patch mainly to start a discussion about it. I
> find it hard to believe that ALL brcmfmac devices support AP scanning
> in which case this feature needs to be limited to those devices
> only. Trouble is there is no FW feature for AP scanning AFAIK.
>
> In any case I think this driver needs to sort out if it supports this
> feature or not, and advertise as such rather than leaving userspace
> in the dark.

By the way, what are the typical use-cases for AP scanning?

I know that hostapd does a passive scan on the AP interface on the
assumption that the driver/firmware will gather channel survey data, but
that's not a universally applicable assumption. Not all implementations
will do that.

Kind regards,
Alvin

>
> diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
> index fb727778312c..b6a50e65dbf6 100644
> --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
> +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
> @@ -7729,6 +7729,8 @@ struct brcmf_cfg80211_info *brcmf_cfg80211_attach(struct brcmf_pub *drvr,
>  #endif
>  	}
>  
> +	wiphy->features |= NL80211_FEATURE_AP_SCAN;
> +
>  	return cfg;
>  
>  detach:

  reply	other threads:[~2022-02-25 22:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 18:18 [PATCH] brcmfmac: include missing AP scan feature James Prestwood
2022-02-25 22:55 ` Alvin Šipraga [this message]
2022-02-25 23:22   ` James Prestwood
2022-02-26 11:27     ` Alvin Šipraga
2022-02-28 17:17       ` James Prestwood
2022-03-02  9:24         ` Arend van Spriel
2022-03-02 17:51           ` James Prestwood

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=87o82ud09z.fsf@bang-olufsen.dk \
    --to=alsi@bang-olufsen.dk \
    --cc=linux-wireless@vger.kernel.org \
    --cc=prestwoj@gmail.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 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.