mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Rosen Penev <rosenp@gmail.com>, linux-wireless@vger.kernel.org
Cc: Jeff Johnson <jjohnson@kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH ath-devel] wifi: ath: split 5150-5350 regulatory rule
Date: Fri, 11 Sep 2026 12:04:25 -0700	[thread overview]
Message-ID: <eaf9335f-ec03-4a3d-8eec-dd788f47a992@oss.qualcomm.com> (raw)
In-Reply-To: <20260904022557.2679261-1-rosenp@gmail.com>

On 9/3/2026 7:25 PM, Rosen Penev wrote:
> Allow initiation in the 5150-5240 MHz portion of the world
> regulatory rule while retaining NO_IR for 5260-5350 MHz, where
> radar detection is required.
> 
> The previous single rule marked both ranges NO_IR and unnecessarily
> restricted channels 36-48. Update the rule counts for the expanded
> rule list.

My understanding is that this is not correct. In world mode the entire 5 GHz
band is restricted since some countries do not allow any transmission in that
band. You must establish that you are in a supported regulatory domain via
802.11d or other mechanisms before transmission.

So I'm dropping this patch from patchwork
> 
> Assisted-by: Codex:gpt-5.6-luna
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
>  drivers/net/wireless/ath/regd.c | 13 +++++++------
>  1 file changed, 7 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/net/wireless/ath/regd.c b/drivers/net/wireless/ath/regd.c
> index f15e7bd690b5..b129af0eed88 100644
> --- a/drivers/net/wireless/ath/regd.c
> +++ b/drivers/net/wireless/ath/regd.c
> @@ -43,7 +43,8 @@ static int __ath_regd_init(struct ath_regulatory *reg);
>  					 NL80211_RRF_NO_OFDM)
>  
>  /* We allow IBSS on these on a case by case basis by regulatory domain */
> -#define ATH_5GHZ_5150_5350	REG_RULE(5150-10, 5350+10, 80, 0, 30,\
> +#define ATH_5GHZ_5150_5350	REG_RULE(5150-10, 5240+10, 80, 0, 30, 0),\
> +				REG_RULE(5260-10, 5350+10, 80, 0, 30,\
>  					 NL80211_RRF_NO_IR)
>  #define ATH_5GHZ_5470_5850	REG_RULE(5470-10, 5850+10, 80, 0, 30,\
>  					 NL80211_RRF_NO_IR)
> @@ -64,7 +65,7 @@ static int __ath_regd_init(struct ath_regulatory *reg);
>  /* Can be used for:
>   * 0x60, 0x61, 0x62 */
>  static const struct ieee80211_regdomain ath_world_regdom_60_61_62 = {
> -	.n_reg_rules = 5,
> +	.n_reg_rules = 6,
>  	.alpha2 =  "99",
>  	.reg_rules = {
>  		ATH_2GHZ_ALL,
> @@ -74,7 +75,7 @@ static const struct ieee80211_regdomain ath_world_regdom_60_61_62 = {
>  
>  /* Can be used by 0x63 and 0x65 */
>  static const struct ieee80211_regdomain ath_world_regdom_63_65 = {
> -	.n_reg_rules = 4,
> +	.n_reg_rules = 5,
>  	.alpha2 =  "99",
>  	.reg_rules = {
>  		ATH_2GHZ_CH01_11,
> @@ -85,7 +86,7 @@ static const struct ieee80211_regdomain ath_world_regdom_63_65 = {
>  
>  /* Can be used by 0x64 only */
>  static const struct ieee80211_regdomain ath_world_regdom_64 = {
> -	.n_reg_rules = 3,
> +	.n_reg_rules = 4,
>  	.alpha2 =  "99",
>  	.reg_rules = {
>  		ATH_2GHZ_CH01_11,
> @@ -95,7 +96,7 @@ static const struct ieee80211_regdomain ath_world_regdom_64 = {
>  
>  /* Can be used by 0x66 and 0x69 */
>  static const struct ieee80211_regdomain ath_world_regdom_66_69 = {
> -	.n_reg_rules = 3,
> +	.n_reg_rules = 4,
>  	.alpha2 =  "99",
>  	.reg_rules = {
>  		ATH_2GHZ_CH01_11,
> @@ -105,7 +106,7 @@ static const struct ieee80211_regdomain ath_world_regdom_66_69 = {
>  
>  /* Can be used by 0x67, 0x68, 0x6A and 0x6C */
>  static const struct ieee80211_regdomain ath_world_regdom_67_68_6A_6C = {
> -	.n_reg_rules = 4,
> +	.n_reg_rules = 5,
>  	.alpha2 =  "99",
>  	.reg_rules = {
>  		ATH_2GHZ_CH01_11,


      reply	other threads:[~2026-09-11 19:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04  2:25 Rosen Penev
2026-09-11 19:04 ` Jeff Johnson [this message]

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=eaf9335f-ec03-4a3d-8eec-dd788f47a992@oss.qualcomm.com \
    --to=jeff.johnson@oss.qualcomm.com \
    --cc=jjohnson@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rosenp@gmail.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

all inboxes | Powered by JetHome®