public inbox for ath12k@lists.infradead.org
 help / color / mirror / Atom feed
From: "Sriram R (QUIC)" <quic_srirrama@quicinc.com>
To: "Jeff Johnson (QUIC)" <quic_jjohnson@quicinc.com>,
	"Sriram R (QUIC)" <quic_srirrama@quicinc.com>,
	"ath12k@lists.infradead.org" <ath12k@lists.infradead.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH 09/12] wifi: ath12k: modify regulatory support for single wiphy architecture
Date: Mon, 15 Jan 2024 07:53:24 +0000	[thread overview]
Message-ID: <565e97fbb0304a268b591a08b891bb4c@quicinc.com> (raw)
In-Reply-To: <9e950030-2781-4fd7-84f1-cb7fd6197e6b@quicinc.com>

>-----Original Message-----
>From: Jeff Johnson (QUIC) <quic_jjohnson@quicinc.com>
>Sent: Friday, January 12, 2024 11:46 PM
>To: Sriram R (QUIC) <quic_srirrama@quicinc.com>; ath12k@lists.infradead.org
>Cc: linux-wireless@vger.kernel.org
>Subject: Re: [PATCH 09/12] wifi: ath12k: modify regulatory support for single wiphy
>architecture
>
>On 1/10/2024 8:50 PM, Sriram R wrote:
>> With all the radios being combined and registered as a single
>> mac80211 hw/wiphy, separate regd built from firmware rules need not be
>> updated to cfg80211. Rather we can pick one of the regd built from the
>> rules to update to cfg80211 for the whole registered device. We prefer
>> 6 GHz pdev based rules since it has the rules for all bands. If the hw
>> doesn't support 6 GHz, then update rules from one of the pdevs.
>
>Do you need to handle the case where there are multiple instances of hardware
>that have divergent regds? I'm thinking of a case where there are 3 underlying
>hardware platforms, one that is 2 GHz, one that is 5 GHz, and one that is 6 GHz, and
>each of them has a regd that only has the rules for the supported band. In such a
>case wouldn't you need to aggregate the rules in the wiphy, not just pick one of the
>sets of rules?
>
>If that is not an expected case, ideally you should describe the requirements &
>assumptions that are in play here.
This is not an expected case with our understanding and testing so far. The 2GHz and 5GHz radio FW
 would pass the regd comprising both 2GHz,  5GHz. The  6GHz FW is passing all of them - 2,5,6GHz, hence
the need to club all the regd info separately is not required. I will make this assumption clear in the next revision.
>
>>
>> Also, when regulatory notification is received, update to all the
>> underlying radios/ar so that it becomes aware of the change and as
>> well us it updates its local regd with the new country rules. Later
>> pick the appropriate pdev's regd(6 GHz if available) and apply to
>> cfg80211.
>
>Here again, can you elaborate on the requirements and assumptions? Do you
>update all channels to each hardware, even if each hardware only supports a
>single band?
By update during reg_notifier here we mean the country code alone to each of the FW
and the channel list update on receiving the regd would update only the corresponding
supported channels to the respective FW and not the combined list.

Thanks,
Sriram.R

  reply	other threads:[~2024-01-15  7:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11  4:50 [PATCH 00/12] wifi: ath12k: Add single wiphy support Sriram R
2024-01-11  4:50 ` [PATCH 01/12] wifi: ath12k: add multiple radio support in a single MAC HW un/register Sriram R
2024-01-12 15:11   ` Jeff Johnson
2024-01-12 17:03   ` Jeff Johnson
2024-01-16  4:45     ` Karthikeyan Periyasamy
2024-01-11  4:50 ` [PATCH 02/12] wifi: ath12k: Modify add and remove chanctx ops for single wiphy support Sriram R
2024-01-12 17:05   ` Jeff Johnson
2024-01-11  4:50 ` [PATCH 03/12] wifi: ath12k: modify ath12k mac start/stop ops for single wiphy Sriram R
2024-01-12 17:07   ` Jeff Johnson
2024-01-11  4:50 ` [PATCH 04/12] wifi: ath12k: vdev statemachine changes " Sriram R
2024-01-12 17:10   ` Jeff Johnson
2024-01-11  4:50 ` [PATCH 05/12] wifi: ath12k: scan " Sriram R
2024-01-12 17:13   ` Jeff Johnson
2024-01-11  4:50 ` [PATCH 06/12] wifi: ath12k: fetch correct radio based on vdev status Sriram R
2024-01-12 17:15   ` Jeff Johnson
2024-01-11  4:50 ` [PATCH 07/12] wifi: ath12k: Cache vdev configs before vdev create Sriram R
2024-01-12 17:23   ` Jeff Johnson
2024-01-13  9:44     ` Kalle Valo
2024-01-11  4:50 ` [PATCH 08/12] wifi: ath12k: Add additional checks for vif and sta iterators Sriram R
2024-01-12 17:26   ` Jeff Johnson
2024-01-11  4:50 ` [PATCH 09/12] wifi: ath12k: modify regulatory support for single wiphy architecture Sriram R
2024-01-12 18:15   ` Jeff Johnson
2024-01-15  7:53     ` Sriram R (QUIC) [this message]
2024-01-11  4:50 ` [PATCH 10/12] wifi: ath12k: Modify set and get antenna mac ops for single wiphy Sriram R
2024-01-12 18:25   ` Jeff Johnson
2024-01-11  4:50 ` [PATCH 11/12] wifi: ath12k: Modify rts threshold mac op " Sriram R
2024-01-12 18:26   ` Jeff Johnson
2024-01-11  4:50 ` [PATCH 12/12] wifi: ath12k: support get_survey " Sriram R
2024-01-12 18:26   ` Jeff Johnson
2024-01-11 20:16 ` [PATCH 00/12] wifi: ath12k: Add single wiphy support Jeff Johnson
2024-01-12  4:34   ` Sriram R (QUIC)
2024-01-12 16:44     ` Jeff Johnson
2024-01-12 18:30       ` 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=565e97fbb0304a268b591a08b891bb4c@quicinc.com \
    --to=quic_srirrama@quicinc.com \
    --cc=ath12k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --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