Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Janusz Dziedzic <janusz.dziedzic@gmail.com>,
	 linux-wireless@vger.kernel.org
Subject: Re: [RFC v5 wireless-next 2/4] wifi: cfg80211: set and report chandef CAC ongoing
Date: Tue, 27 Jan 2026 14:02:14 +0100	[thread overview]
Message-ID: <69c37195aaedd7933bcc307aadbc12d1cdf85b33.camel@sipsolutions.net> (raw)
In-Reply-To: <20260125160353.34102-3-janusz.dziedzic@gmail.com> (sfid-20260125_170409_804588_262B2BFE)

On Sun, 2026-01-25 at 17:00 +0100, Janusz Dziedzic wrote:
> 
> + * @cac_ongoing_time: timestamp (CLOCK_BOOTTIME, nanoseconds) when CAC was
> + *	started on this channel. Zero when CAC is not in progress.

Is "ongoing" really a good name? To me something like "CAC start
timestamp" would seem more descriptive?

>   * @psd: power spectral density (in dBm)
>   */
>  struct ieee80211_channel {
> @@ -205,6 +207,7 @@ struct ieee80211_channel {
>  	enum nl80211_dfs_state dfs_state;
>  	unsigned long dfs_state_entered;
>  	unsigned int dfs_cac_ms;
> +	u64 cac_ongoing_time;
>  	s8 psd;
>  };
>  
> diff --git a/include/uapi/linux/nl80211.h b/include/uapi/linux/nl80211.h
> index b0f050e36fa4..7c23fd1b8ce9 100644
> --- a/include/uapi/linux/nl80211.h
> +++ b/include/uapi/linux/nl80211.h
> @@ -4452,6 +4452,10 @@ enum nl80211_wmm_rule {
>   * @NL80211_FREQUENCY_ATTR_S1G_NO_PRIMARY: Channel is not permitted for use
>   *	as a primary channel. Does not prevent the channel from existing
>   *	as a non-primary subchannel. Only applicable to S1G channels.
> + * @NL80211_FREQUENCY_ATTR_CAC_START_TIME: Channel Availability Check (CAC)
> + *	start time (CLOCK_BOOTTIME, nanoseconds). Only present when CAC is
> + *	currently in progress on this channel.

And here it _is_ "CAC start time".


johannes

  reply	other threads:[~2026-01-27 13:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-25 16:00 [RFC v5 wireless-next 0/4] background CAC fixes Janusz Dziedzic
2026-01-25 16:00 ` [RFC v5 wireless-next 1/4] wifi: cfg80211: fix background CAC Janusz Dziedzic
2026-01-25 16:00 ` [RFC v5 wireless-next 2/4] wifi: cfg80211: set and report chandef CAC ongoing Janusz Dziedzic
2026-01-27 13:02   ` Johannes Berg [this message]
2026-01-25 16:00 ` [RFC v5 wireless-next 3/4] wifi: cfg80211: events, report background radar Janusz Dziedzic
2026-01-25 16:00 ` [RFC v5 wireless-next 4/4] wifi: mac80211_hwsim: background CAC support Janusz Dziedzic
2026-01-27 13:07   ` Johannes Berg

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=69c37195aaedd7933bcc307aadbc12d1cdf85b33.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=janusz.dziedzic@gmail.com \
    --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