From: Johannes Berg <johannes@sipsolutions.net>
To: mpubbise@codeaurora.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211: advertise supported interface types for sw encryption
Date: Thu, 22 Mar 2018 09:06:15 +0100 [thread overview]
Message-ID: <1521705975.6713.1.camel@sipsolutions.net> (raw)
In-Reply-To: <089d864c1d6bb9218191dad53713f148@codeaurora.org>
On Thu, 2018-03-22 at 11:51 +0530, mpubbise@codeaurora.org wrote:
>
> > So IMHO - just get rid of the bitmap and hard-code AP_VLAN.
> >
>
> I agree with you only partially.
>
> Today, I do not see any driver advertising SW_CRYPTO_CONTROL other than
> ath10k. There could be some driver which would want to advertise
> SW_CRYPTO_CONTROL and do not support the software encryption for VLAN
> devices. In that case, hard-coding doesn't seem to solve the problem
> completely right? No?
Well, my point is that such a hypothetical driver is completely
irrelevant because it doesn't make any sense to have this behaviour -
it would mean it cannot support AP_VLAN with encryption, so it might as
well not support AP_VLAN at all.
> Or you meant to say that driver should advertise the support for
> AP_VLANs only if it can support encryption on AP_VLAN devices?
Right.
> If this
> the case, then I could see some code in ieee80211_register_hw which says
> this,
>
> /* if low-level driver supports AP, we also support VLAN */
> if (local->hw.wiphy->interface_modes & BIT(NL80211_IFTYPE_AP)) {
> hw->wiphy->interface_modes |=
> BIT(NL80211_IFTYPE_AP_VLAN);
> hw->wiphy->software_iftypes |=
> BIT(NL80211_IFTYPE_AP_VLAN);
> }
Yes, but if such a driver comes along we can change this.
johannes
next prev parent reply other threads:[~2018-03-22 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 6:27 [RFC] mac80211: advertise supported interface types for sw encryption mpubbise
2018-03-21 7:53 ` Johannes Berg
2018-03-22 6:21 ` mpubbise
2018-03-22 8:06 ` Johannes Berg [this message]
2018-03-23 5:51 ` mpubbise
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=1521705975.6713.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mpubbise@codeaurora.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).