From: Johannes Berg <johannes@sipsolutions.net>
To: Aditya Kumar Singh <quic_adisi@quicinc.com>, ath11k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org, Jeff Johnson <quic_jjohnson@quicinc.com>
Subject: Re: [PATCH v2 1/3] wifi: cfg80211: export DFS CAC time and usable state helper functions
Date: Wed, 13 Sep 2023 12:17:38 +0200 [thread overview]
Message-ID: <365caa2a20678c1c1c08c947a2141b40320553c6.camel@sipsolutions.net> (raw)
In-Reply-To: <511f23be-7b7b-42d9-9c3e-25edfa5d7323@quicinc.com>
On Wed, 2023-09-13 at 15:46 +0530, Aditya Kumar Singh wrote:
> On 9/13/23 14:58, Johannes Berg wrote:
> > On Tue, 2023-09-12 at 10:48 +0530, 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.
> > >
> >
> > Should we really export the time function just for a debug messages?
> > That seems like a waste of space?
> >
> Yes absolutely. But actually as a follow up of this patch, we have
> Background DFS patch in pipeline which requires us to send the CAC time
> to firmware. So its actually needed there. And may be once we do this,
> other drivers also may start using this?
OK, fair enough :)
johannes
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2023-09-13 10:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 5:18 [PATCH v2 0/3] wifi: ath11k: fix CAC running state Aditya Kumar Singh
2023-09-12 5:18 ` [PATCH v2 1/3] wifi: cfg80211: export DFS CAC time and usable state helper functions Aditya Kumar Singh
2023-09-12 17:50 ` Jeff Johnson
2023-09-13 9:28 ` Johannes Berg
2023-09-13 10:16 ` Aditya Kumar Singh
2023-09-13 10:17 ` Johannes Berg [this message]
2023-09-12 5:18 ` [PATCH v2 2/3] wifi: ath11k: fix CAC running state during virtual interface start Aditya Kumar Singh
2023-09-12 17:51 ` Jeff Johnson
2023-10-05 6:23 ` Kalle Valo
2023-09-12 5:18 ` [PATCH v2 3/3] wifi: ath11k: fix Tx power value during active CAC Aditya Kumar Singh
2023-09-12 17:52 ` Jeff Johnson
2023-10-03 14:31 ` Kalle Valo
2023-10-04 2:09 ` Aditya Kumar Singh
2023-10-04 4:54 ` Kalle Valo
2023-10-04 4:54 ` Aditya Kumar Singh
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=365caa2a20678c1c1c08c947a2141b40320553c6.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_adisi@quicinc.com \
--cc=quic_jjohnson@quicinc.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 read-only IMAP folder(s) and NNTP newsgroup(s).