From: Aditya Kumar Singh <quic_adisi@quicinc.com>
To: <ath11k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>, <johannes@sipsolutions.net>
Subject: Re: [PATCH 1/3] wifi: cfg80211: export DFS CAC time and usable state helper functions
Date: Thu, 27 Jul 2023 17:35:28 +0530 [thread overview]
Message-ID: <5e45705e-b1d1-a0dc-2c3d-455fb433e93f@quicinc.com> (raw)
In-Reply-To: <20230607124647.27682-2-quic_adisi@quicinc.com>
On 6/7/2023 18:16, Aditya Kumar Singh wrote:
> cfg80211 has cfg80211_chandef_dfs_usable() function to know whether
> at least one channel in the chandef is in usable state or not. Also,
> cfg80211_chandef_dfs_cac_time() function is there which tells the CAC
> time required for the given chandef.
>
> Make these two functions visible to drivers by exporting their symbol
> to global list of kernel symbols.
>
> Lower level drivers can make use of these two functions to be aware
> if CAC is required on the given chandef and for how long. For example
> drivers which maintains the CAC state internally can make use of these.
>
> Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com>
> ---
Hi Johannes,
Do you have any comments for this patch?
- Aditya
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2023-07-27 12:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 12:46 [PATCH 0/3] wifi: ath11k: fix CAC running state Aditya Kumar Singh
2023-06-07 12:46 ` [PATCH 1/3] wifi: cfg80211: export DFS CAC time and usable state helper functions Aditya Kumar Singh
2023-07-27 12:05 ` Aditya Kumar Singh [this message]
2023-07-27 16:29 ` Kalle Valo
2023-08-22 15:01 ` Jeff Johnson
2023-06-07 12:46 ` [PATCH 2/3] wifi: ath11k: fix CAC running state during virtual interface start Aditya Kumar Singh
2023-08-22 15:02 ` Jeff Johnson
2023-09-13 13:25 ` Aditya Kumar Singh
2023-09-14 13:16 ` Kalle Valo
2023-06-07 12:46 ` [PATCH 3/3] wifi: ath11k: fix Tx power value during active CAC Aditya Kumar Singh
2023-08-22 15:03 ` Jeff Johnson
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=5e45705e-b1d1-a0dc-2c3d-455fb433e93f@quicinc.com \
--to=quic_adisi@quicinc.com \
--cc=ath11k@lists.infradead.org \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).