ath12k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
To: <ath12k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>,
	Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
Subject: [PATCH 1/4] wifi: ath12k: Refactor the DP pdev pre alloc call sequence
Date: Wed, 6 Dec 2023 09:19:17 +0530	[thread overview]
Message-ID: <20231206034920.1037449-2-quic_periyasa@quicinc.com> (raw)
In-Reply-To: <20231206034920.1037449-1-quic_periyasa@quicinc.com>

Currently, the data path pdev pre alloc and mac allocate are called
separately from the core start procedure. The data path pdev pre alloc
can be called from the mac allocate procedure itself since initialization
related to pdev happens in the mac allocate procedure. So move the caller
of DP pdev pre alloc from the core start procedure to the mac allocate
procedure. This change helps in the future to easily decouple the mac
allocate procedure from core start handling in order to support MLO in
multi chip.

Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1

Signed-off-by: Karthikeyan Periyasamy <quic_periyasa@quicinc.com>
---
 drivers/net/wireless/ath/ath12k/core.c | 2 --
 drivers/net/wireless/ath/ath12k/mac.c  | 2 ++
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/net/wireless/ath/ath12k/core.c b/drivers/net/wireless/ath/ath12k/core.c
index 6c01b282fcd3..6f634b57dde8 100644
--- a/drivers/net/wireless/ath/ath12k/core.c
+++ b/drivers/net/wireless/ath/ath12k/core.c
@@ -592,8 +592,6 @@ static int ath12k_core_start(struct ath12k_base *ab,
 
 	ath12k_dp_cc_config(ab);
 
-	ath12k_dp_pdev_pre_alloc(ab);
-
 	ret = ath12k_dp_rx_pdev_reo_setup(ab);
 	if (ret) {
 		ath12k_err(ab, "failed to initialize reo destination rings: %d\n", ret);
diff --git a/drivers/net/wireless/ath/ath12k/mac.c b/drivers/net/wireless/ath/ath12k/mac.c
index 88cec54c6c2e..49d56f5d8896 100644
--- a/drivers/net/wireless/ath/ath12k/mac.c
+++ b/drivers/net/wireless/ath/ath12k/mac.c
@@ -7667,6 +7667,8 @@ int ath12k_mac_allocate(struct ath12k_base *ab)
 		clear_bit(ATH12K_FLAG_MONITOR_ENABLED, &ar->monitor_flags);
 	}
 
+	ath12k_dp_pdev_pre_alloc(ab);
+
 	return 0;
 
 err_free_mac:
-- 
2.34.1



  reply	other threads:[~2023-12-06  3:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06  3:49 [PATCH 0/4] wifi: ath12k: Refactor MAC alloc/destroy/un/register helper functions Karthikeyan Periyasamy
2023-12-06  3:49 ` Karthikeyan Periyasamy [this message]
2023-12-08  0:22   ` [PATCH 1/4] wifi: ath12k: Refactor the DP pdev pre alloc call sequence Jeff Johnson
2024-01-16 12:20   ` Kalle Valo
2023-12-06  3:49 ` [PATCH 2/4] wifi: ath12k: Refactor the MAC allocation and destroy Karthikeyan Periyasamy
2023-12-08  0:22   ` Jeff Johnson
2023-12-06  3:49 ` [PATCH 3/4] wifi: ath12k: Refactor MAC setup channel helper function Karthikeyan Periyasamy
2023-12-08  0:22   ` Jeff Johnson
2023-12-06  3:49 ` [PATCH 4/4] wifi: ath12k: Refactor MAC un/register " Karthikeyan Periyasamy
2023-12-08  0:23   ` Jeff Johnson
2024-01-09 13:25   ` Kalle Valo
2024-01-09 13:41     ` Karthikeyan Periyasamy
2024-01-15 15:27       ` Kalle Valo
2024-01-16  4:49         ` Karthikeyan Periyasamy

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=20231206034920.1037449-2-quic_periyasa@quicinc.com \
    --to=quic_periyasa@quicinc.com \
    --cc=ath12k@lists.infradead.org \
    --cc=linux-wireless@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).