From: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: igor.mitsyanko.os@quantenna.com, linux-wireless@vger.kernel.org,
Avinash Patil <avinashp@quantenna.com>
Subject: Re: [PATCH v6] qtnfmac: introduce new FullMAC driver for Quantenna chipsets
Date: Sun, 21 May 2017 20:08:15 +0300 [thread overview]
Message-ID: <20170521170814.d7ljne2pgopymxud@bars> (raw)
In-Reply-To: <1495189094.3274.2.camel@sipsolutions.net>
On Fri, May 19, 2017 at 12:18:14PM +0200, Johannes Berg wrote:
> FWIW, regarding the qtnf_mgmt_frame_register() and
> cfg80211_rx_mgmt() thing, I think we'll have to discuss how to do this,
> and perhaps you need to think about the firmware API for it.
>
> Right now, I don't see that you can pass filters down, but you probably
> also don't want to implement the reject code in the driver? And
> cfg80211 doesn't give you that data right now either... So somewhere I
> expect we'll need to make changes, unless you just copy (e.g. from
> mac80211) the implementation of what happens when cfg80211_rx_mgmt()
> returns false.
Thanks for pointing at mac80211 reject code. In our specific case
it looks like the issue can be fixed with help of the following
building blocks:
- properly set NL80211_RXMGMT_FLAG_ANSWERED flag, since quite a few
mgmt frame types are completely handled by firmware
- reply to action frames rejected by userspace tools
in the same way as it is done by mac80211
Adding reject code seems to be straightforward. Adding NL80211_RXMGMT_FLAG_ANSWERED
flag to firmware is a more involved task. But it can be done gradually, from
simple usecases to the complicated ones. Besides, IIUC the support of this flag
by userspace tools is still a work in progress. E.g., hostapd is not yet using it,
so we keep using 'send_probe_response = 0' config option.
In the long run the idea of passing mgmt frame filters to drivers looks
appealing. It will be up to driver whether to use filters (e.g. pass them
to firmware for early processing) or not to use them (essentially leaving
it for cfg80211 subsystem). I did a quick search through other users of
cfg80211_rx_mgmt among wireless drivers. It turns out that none of them is
checking its return value. So there may be other potential
users of this feature :)
Does it make sense if I post an RFC patch modifying current interface
of mgmt_frame_register in cfg80211_ops to collect feedback ?
Regards,
Sergey
next prev parent reply other threads:[~2017-05-21 17:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 21:51 [PATCH v6] qtnfmac: introduce new FullMAC driver for Quantenna chipsets igor.mitsyanko.os
2017-05-12 15:18 ` [v6] " Kalle Valo
2017-05-12 15:20 ` Kalle Valo
2017-05-12 15:43 ` Joe Perches
2017-05-12 16:37 ` Kalle Valo
2017-05-12 17:47 ` Igor Mitsyanko
2017-05-17 13:12 ` [PATCH v6] " Johannes Berg
2017-05-18 20:08 ` Sergey Matyukevich
2017-05-19 10:18 ` Johannes Berg
2017-05-21 17:08 ` Sergey Matyukevich [this message]
2017-05-22 6:28 ` Johannes Berg
2017-05-22 21:04 ` Sergey Matyukevich
2017-05-24 7:11 ` Johannes Berg
2017-05-24 11:08 ` Sergey Matyukevich
2017-05-22 9:09 ` Kalle Valo
2017-05-24 14:06 ` [v6] " Kalle Valo
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=20170521170814.d7ljne2pgopymxud@bars \
--to=sergey.matyukevich.os@quantenna.com \
--cc=avinashp@quantenna.com \
--cc=igor.mitsyanko.os@quantenna.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).