mirror of https://lore.kernel.org/ath12k/
 help / color / mirror / Atom feed
From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Rameshkumar Sundaram <quic_ramess@quicinc.com>,
	<ath12k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>, Sriram R <quic_srirrama@quicinc.com>
Subject: Re: [PATCH v6 00/12] wifi: ath12k: Add single wiphy suppor
Date: Mon, 1 Apr 2024 12:34:20 -0700	[thread overview]
Message-ID: <0d1058eb-aced-4e81-9f61-e4b5a08c04a2@quicinc.com> (raw)
In-Reply-To: <20240401190409.2461819-1-quic_ramess@quicinc.com>

On 4/1/2024 12:03 PM, Rameshkumar Sundaram wrote:
> From: Sriram R <quic_srirrama@quicinc.com>
> 
> With the introduction of Multi Link Operation (MLO) support in
> IEEE802.11be, each EHT AP/non AP interface is capable of
> operating with multiple radio links.
> 
> cfg80211/mac80211 expects drivers to abstract the communication
> between such Multi Link HW and mac80211/cfg80211 since it depends
> on different driver/HW implementation. Hence the single wiphy
> abstraction with changes in datastructures were introduced in
> "wifi: ath12k: Introduce hw abstraction"
> 
> This patchset extends the implementation to allow combination
> of multiple underlying radios into a single composite hw/wiphy
> for registration. Since now multiple radios are represented by
> a single wiphy, changes are required in various mac ops that the
> driver supports since the driver now needs to learn on how to tunnel
> various mac ops properly to a specific radio.
> 
> This patchset covers the basic mac80211 ops for an interface bring up
> and operation.
> 
> Note:
> Monitor and hw reconfig support for Single Wiphy will be done in future
> patchsets.

thinking about this series in the context of some other patches I've been
reviewing recently, I don't think this series should be talking about
supporting multiple radios with a single wiphy, but instead about supporting
multiple devices with a single wiphy. After all, the existing logic already
supports a single device with multiple radios, so it isn't the multitude of
radios that is the issue, it is the multitude of devices.

this would have ramifications on many of the commit messages in this series.



  parent reply	other threads:[~2024-04-01 19:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 19:03 [PATCH v6 00/12] wifi: ath12k: Add single wiphy suppor Rameshkumar Sundaram
2024-04-01 19:03 ` [PATCH v6 01/12] wifi: ath12k: add multiple radio support in a single MAC HW un/register Rameshkumar Sundaram
2024-04-01 19:03 ` [PATCH v6 02/12] wifi: ath12k: Modify add and remove chanctx ops for single wiphy support Rameshkumar Sundaram
2024-04-01 19:04 ` [PATCH v6 03/12] wifi: ath12k: modify ath12k mac start/stop ops for single wiphy Rameshkumar Sundaram
2024-04-01 19:04 ` [PATCH v6 04/12] wifi: ath12k: vdev statemachine changes " Rameshkumar Sundaram
2024-04-01 19:04 ` [PATCH v6 05/12] wifi: ath12k: scan " Rameshkumar Sundaram
2024-04-01 19:04 ` [PATCH v6 06/12] wifi: ath12k: fetch correct radio based on vdev status Rameshkumar Sundaram
2024-04-01 19:04 ` [PATCH v6 07/12] wifi: ath12k: Cache vdev configs before vdev create Rameshkumar Sundaram
2024-04-01 19:26   ` Jeff Johnson
2024-04-02 10:14     ` Rameshkumar Sundaram
2024-04-01 19:04 ` [PATCH v6 08/12] wifi: ath12k: Add additional checks for vif and sta iterators Rameshkumar Sundaram
2024-04-01 19:04 ` [PATCH v6 09/12] wifi: ath12k: modify regulatory support for single wiphy architecture Rameshkumar Sundaram
2024-04-01 19:04 ` [PATCH v6 10/12] wifi: ath12k: Modify set and get antenna mac ops for single wiphy Rameshkumar Sundaram
2024-04-01 19:04 ` [PATCH v6 11/12] wifi: ath12k: Modify rts threshold mac op " Rameshkumar Sundaram
2024-04-01 19:04 ` [PATCH v6 12/12] wifi: ath12k: support get_survey " Rameshkumar Sundaram
2024-04-01 19:34 ` Jeff Johnson [this message]
2024-04-02 10:06   ` [PATCH v6 00/12] wifi: ath12k: Add single wiphy suppor Rameshkumar Sundaram
2024-04-05  2:12     ` Rameshkumar Sundaram
2024-04-05 15:36       ` 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=0d1058eb-aced-4e81-9f61-e4b5a08c04a2@quicinc.com \
    --to=quic_jjohnson@quicinc.com \
    --cc=ath12k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=quic_ramess@quicinc.com \
    --cc=quic_srirrama@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