linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Dmitrii Lebed <dlebed@quantenna.com>,
	Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>,
	linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Igor Mitsyanko <igor.mitsyanko.os@quantenna.com>,
	Avinash Patil <avinashp@quantenna.com>
Subject: Re: [PATCH] cfg80211/nl80211: add DFS offload flag
Date: Wed, 21 Feb 2018 20:59:26 +0100	[thread overview]
Message-ID: <5A8DCF9E.90505@broadcom.com> (raw)
In-Reply-To: <0e3d5af0-bc6b-d98f-02f2-cc4d585e6cd1@quantenna.com>

On 2/21/2018 12:25 PM, Dmitrii Lebed wrote:
>
> On 21.02.2018 14:03, Arend van Spriel wrote:
>> On 2/21/2018 11:56 AM, Sergey Matyukevich wrote:
>>> From: Dmitry Lebed <dlebed@quantenna.com>
>>>
>>> Add wiphy flag to indicate that HW does all DFS actions by itself.
>>> User-space functionality already implemented in hostapd using
>>> vendor-specific (QCA) OUI to advertise HW support.
>>> Need to introduce generic flag to inform about DFS offload support.
>>> For deivces with DFS_OFFLOAD flag set user-space will no longer
>>> need to issue CAC or do any actions in response to
>>> "radar detected" events. HW will do everything by itself and send
>>> events to user-space to idicate that CAC was started/finished, etc.
>>>
>>> Signed-off-by: Dmitrii Lebed <dlebed@quantenna.com>
>>> ---
>>>   include/net/cfg80211.h       | 7 ++++++-
>>>   include/uapi/linux/nl80211.h | 9 +++++++++
>>>   net/wireless/nl80211.c       | 7 +++++++
>>>   3 files changed, 22 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h
>>> index ed3a28105d6c..b2d17993ae4d 100644
>>> --- a/include/net/cfg80211.h
>>> +++ b/include/net/cfg80211.h
>>> @@ -3241,6 +3241,11 @@ struct cfg80211_ops {
>>>    * @WIPHY_FLAG_IBSS_RSN: The device supports IBSS RSN.
>>>    * @WIPHY_FLAG_MESH_AUTH: The device supports mesh authentication
>>> by routing
>>>    *  auth frames to userspace. See @NL80211_MESH_SETUP_USERSPACE_AUTH.
>>> + * @WIPHY_FLAG_DFS_OFFLOAD: Device will do all DFS-related actions
>>> by itself,
>>> + *   informing user-space about CAC progress, radar detection event,
>>> + *   channel change triggered by radar detection event.
>>> + *   No need to start CAC from user-space, no need to react to
>>> + *   "radar detected" event.
>>
>> wiphy flags are kinda deprecated. At least no new flags should be added.
>> Instead use EXT_FEATURE flag.
>>
>> Regards,
>> Arend
> Thanks for clarification, Arend. I'll change it to use new EXT_FEATURE
> flag.
> BTW, are there any concerns regarding adding generic DFS_OFFLOAD driver
> capability?
> I want to add DFS_OFFLOAD support to qtnfmac driver and fix hostapd to
> support
> generic EXT_FEATURE flag as well as vendor-specific capabilities.

I suppose you are referring to the qcom vendor-specific stuff for DFS 
offload. I can not speak for Kalle nor Johannes, but you have my thumbs 
up. I am not familiar enough with the qcom implementation to say whether 
there are concerns.

> Thanks,
> Dmitrii
>>
>>>    * @WIPHY_FLAG_SUPPORTS_FW_ROAM: The device supports roaming
>>> feature in the
>>>    *  firmware.
>>>    * @WIPHY_FLAG_AP_UAPSD: The device supports uapsd on AP.
>>
>
>
> This email, including its contents and any attachment(s), may contain
> confidential information of Quantenna Communications, Inc. and is solely
> for the intended recipient(s). If you may have received this in error,
> please contact the sender and permanently delete this email, its
> contents and any attachment(s).

Friendly advice: you may want to avoid using this footer in emails on 
the kernel.org mailing lists.

Regards,
Arend

  reply	other threads:[~2018-02-21 19:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-21 10:56 [PATCH] cfg80211/nl80211: add DFS offload flag Sergey Matyukevich
2018-02-21 11:03 ` Arend van Spriel
2018-02-21 11:25   ` Dmitrii Lebed
2018-02-21 19:59     ` Arend van Spriel [this message]
2018-02-22  7:57       ` Kalle Valo
2018-02-22  8:23         ` Sergey Matyukevich
2018-02-27  8:40           ` 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=5A8DCF9E.90505@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=avinashp@quantenna.com \
    --cc=dlebed@quantenna.com \
    --cc=igor.mitsyanko.os@quantenna.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sergey.matyukevich.os@quantenna.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;
as well as URLs for NNTP newsgroup(s).