Netdev List
 help / color / mirror / Atom feed
From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: TangYi <1914018426@qq.com>, linux-wireless@vger.kernel.org
Cc: netdev@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: [PATCH] wifi: cfg80211: allow IR on a channel the wiphy already operates on
Date: Mon, 12 Oct 2026 07:11:24 -0700	[thread overview]
Message-ID: <52d0917d-49c3-4d24-b43e-d9321d8e1a2e@oss.qualcomm.com> (raw)
In-Reply-To: <tencent_B6DCCE2CE592B4FCCDD65E6D07A91C4D6307@qq.com>

On 10/12/2026 6:42 AM, TangYi wrote:
> On Mon, 2026-10-12 at 20:59 +0800, Johannes Berg wrote:
>> This isn't how regulatory works, sorry.
> 
> Thanks for the correction - the "already radiating" argument was the
> wrong frame, please disregard that reasoning.
> 
> Let me ask the constructive version, with the concrete observation that
> led me here. On this iwlwifi device (Meteor Lake CNVi, firmware in LAR),
> after the station associates on ch149:
> 
>  - iw reg get (phy section) shows the learned domain marking
>    5735-5775 MHz as IR-CONCURRENT;
> 
>  - iw phy shows channel 5745 with plain "no IR" and no IR_CONCURRENT
>    flag;
> 
>  - and the iwlwifi source contains no IR_CONCURRENT handling at all.
> 
> So the domain rules and the per-channel flags disagree, and the
> reg_can_beacon relaxation cannot trigger (it requires the channel
> flag). Should the driver be propagating the domain's IR_CONCURRENT rule
> onto the channel flags once the firmware has a usable domain? Or is AP
> operation on such channels simply not intended until a country is
> learned?
> 
> Happy to take this to the iwlwifi side if that's where the fix belongs.
> 
> TangYi

off topic: you need to figure out your mail agent since this reply was not
threaded properly.

It indicates In-Reply-To: <20261012125955.1519379-1-1914018426@qq.com> but
that was not the Message-Id of either your patch or Johannes' reply.


  reply	other threads:[~2026-10-12 14:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20261012125955.1519379-1-1914018426@qq.com>
2026-10-12 13:42 ` [PATCH] wifi: cfg80211: allow IR on a channel the wiphy already operates on TangYi
2026-10-12 14:11   ` Jeff Johnson [this message]
2026-10-12 12:59 TangYi
2026-10-12 13:35 ` Johannes Berg
2026-10-12 14:42   ` TangYi
2026-10-13 13:55 ` netdev-bot+sashiko

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=52d0917d-49c3-4d24-b43e-d9321d8e1a2e@oss.qualcomm.com \
    --to=jeff.johnson@oss.qualcomm.com \
    --cc=1914018426@qq.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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