From: Vasanthakumar Thiagarajan <vasanthakumar.thiagarajan@oss.qualcomm.com>
To: Ripan Deuri <quic_rdeuri@quicinc.com>, ath12k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH ath12k-ng v2 0/2] wifi: ath12k: Modularization of PDEV object for Next Generation Driver
Date: Wed, 8 Oct 2025 21:22:13 +0530 [thread overview]
Message-ID: <a3b8334e-c3bf-015b-540e-d6962ecfaa4f@oss.qualcomm.com> (raw)
In-Reply-To: <20251007110203.1541167-1-quic_rdeuri@quicinc.com>
On 10/7/2025 4:32 PM, Ripan Deuri wrote:
> This patch series continues the effort to modularize data path structures
> in ath12k, focusing on improving the organization of DP pdev handling and
> preparing for future architecture-specific extensions.
>
> Patch 1 refactors DP pdev handling by consolidating all DP-related fields
> of a radio into struct ath12k_pdev_dp structure. An RCU-protected array of
> these objects is introduced in ath12k_dp to facilitate dp_pdev lookup from
> ath12k_dp.
>
> Patch 2 encapsulates PPDU statistics within dp_pdev, as these stats are
> associated with out-of-band data path operations. This reorganization
> provides a cleaner structure by grouping both in-band (per-packet) fields
> and out-of-band stats under the same ath12k_pdev_dp object.
>
> These changes are part of a broader effort to establish a base framework
> for next-generation driver development, allowing the data path to remain
> flexible for future extensions.
> ---
> Changes in v2:
> - Made ath12k_pdev_dp_to_ar() a static inline in core.h
> ---
> Ripan Deuri (2):
> wifi: ath12k: Refactor data path pdev struct
> wifi: ath12k: Rearrange PPDU radio stats
>
> drivers/net/wireless/ath/ath12k/core.h | 24 +-
> drivers/net/wireless/ath/ath12k/dp.c | 23 ++
> drivers/net/wireless/ath/ath12k/dp.h | 41 ++++
> drivers/net/wireless/ath/ath12k/dp_cmn.h | 18 ++
> drivers/net/wireless/ath/ath12k/dp_htt.c | 59 +++--
> drivers/net/wireless/ath/ath12k/dp_mon.c | 183 ++++++++-------
> drivers/net/wireless/ath/ath12k/dp_mon.h | 9 +-
> drivers/net/wireless/ath/ath12k/dp_rx.c | 99 ++++----
> drivers/net/wireless/ath/ath12k/dp_rx.h | 13 +-
> drivers/net/wireless/ath/ath12k/mac.c | 34 ++-
> drivers/net/wireless/ath/ath12k/wifi7/dp_rx.c | 216 ++++++++++--------
> drivers/net/wireless/ath/ath12k/wifi7/dp_tx.c | 66 +++---
> drivers/net/wireless/ath/ath12k/wifi7/dp_tx.h | 2 +-
> 13 files changed, 488 insertions(+), 299 deletions(-)
Reviewed-by: Vasanthakumar Thiagarajan <vasanthakumar.thiagarajan@oss.qualcomm.com>
next prev parent reply other threads:[~2025-10-08 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 11:02 [PATCH ath12k-ng v2 0/2] wifi: ath12k: Modularization of PDEV object for Next Generation Driver Ripan Deuri
2025-10-07 11:02 ` [PATCH ath12k-ng v2 1/2] wifi: ath12k: Refactor data path pdev struct Ripan Deuri
2025-10-07 11:02 ` [PATCH ath12k-ng v2 2/2] wifi: ath12k: Rearrange PPDU radio stats Ripan Deuri
2025-10-08 15:52 ` Vasanthakumar Thiagarajan [this message]
2025-10-08 16:28 ` [PATCH ath12k-ng v2 0/2] wifi: ath12k: Modularization of PDEV object for Next Generation Driver 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=a3b8334e-c3bf-015b-540e-d6962ecfaa4f@oss.qualcomm.com \
--to=vasanthakumar.thiagarajan@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_rdeuri@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