From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
To: kvalo@kernel.org, jjohnson@kernel.org,
linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: quic_cjhuang@quicinc.com, jtornosm@redhat.com,
Vladimir Benes <vbenes@redhat.com>
Subject: [PATCH] wifi: ath11k: allow APs combination when dual stations are supported
Date: Mon, 2 Dec 2024 10:18:30 +0100 [thread overview]
Message-ID: <20241202091858.200773-1-jtornosm@redhat.com> (raw)
Since commit f019f4dff2e4 ("wifi: ath11k: support 2 station interfaces"),
if dual stations are supported for a device, we can not configure more that
one AP and/or DFS cannot be enabled.
Enable this by creating a new parameter (ignore_support_dual_stations) to
ignore this feature if it is convenient. Default behavior is to support
dual stations if possible.
Reported-by: Vladimir Benes <vbenes@redhat.com>
Signed-off-by: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
---
drivers/net/wireless/ath/ath11k/core.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/drivers/net/wireless/ath/ath11k/core.c b/drivers/net/wireless/ath/ath11k/core.c
index be67382c00f6..55c7a55d85ff 100644
--- a/drivers/net/wireless/ath/ath11k/core.c
+++ b/drivers/net/wireless/ath/ath11k/core.c
@@ -37,6 +37,12 @@ bool ath11k_ftm_mode;
module_param_named(ftm_mode, ath11k_ftm_mode, bool, 0444);
MODULE_PARM_DESC(ftm_mode, "Boots up in factory test mode");
+static bool ath11k_ignore_support_dual_stations;
+module_param_named(ignore_support_dual_stations,
+ ath11k_ignore_support_dual_stations, bool, 0644);
+MODULE_PARM_DESC(ignore_support_dual_stations,
+ "Ignore the support for dual stations to support other combinations");
+
static const struct ath11k_hw_params ath11k_hw_params[] = {
{
.hw_rev = ATH11K_HW_IPQ8074,
@@ -2162,6 +2168,9 @@ static int ath11k_init_hw_params(struct ath11k_base *ab)
}
ab->hw_params = *hw_params;
+ if (ab->hw_params.support_dual_stations &&
+ ath11k_ignore_support_dual_stations)
+ ab->hw_params.support_dual_stations = false;
ath11k_info(ab, "%s\n", ab->hw_params.name);
--
2.47.0
next reply other threads:[~2024-12-02 9:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 9:18 Jose Ignacio Tornos Martinez [this message]
2024-12-03 1:54 ` [PATCH] wifi: ath11k: allow APs combination when dual stations are supported Yu Zhang (Yuriy)
2024-12-03 8:04 ` Jose Ignacio Tornos Martinez
2024-12-03 8:28 ` Yu Zhang (Yuriy)
2024-12-03 9:48 ` Jose Ignacio Tornos Martinez
2024-12-03 10:48 ` Yu Zhang (Yuriy)
2024-12-03 16:33 ` Jose Ignacio Tornos Martinez
2024-12-04 3:21 ` Yu Zhang (Yuriy)
2024-12-04 7:51 ` Jose Ignacio Tornos Martinez
2024-12-04 8:30 ` Jose Ignacio Tornos Martinez
2024-12-04 9:18 ` Yu Zhang (Yuriy)
2024-12-05 11:07 ` Jose Ignacio Tornos Martinez
2024-12-06 2:24 ` Yu Zhang (Yuriy)
2024-12-08 12:13 ` Jose Ignacio Tornos Martinez
2024-12-09 2:29 ` Yu Zhang (Yuriy)
2024-12-09 8:03 ` Jose Ignacio Tornos Martinez
2024-12-09 8:33 ` Yu Zhang (Yuriy)
2024-12-10 8:44 ` Jose Ignacio Tornos Martinez
2024-12-11 2:10 ` Yu Zhang (Yuriy)
2024-12-11 17:41 ` Jose Ignacio Tornos Martinez
2025-01-14 18:34 ` Jose Ignacio Tornos Martinez
2025-01-15 8:59 ` Yu Zhang (Yuriy)
2025-01-15 9:46 ` Jose Ignacio Tornos Martinez
2025-01-15 10:48 ` Yu Zhang (Yuriy)
2025-01-15 11:06 ` Jose Ignacio Tornos Martinez
2025-01-15 11:20 ` Yu Zhang (Yuriy)
2025-01-15 11:55 ` Jose Ignacio Tornos Martinez
2025-01-15 12:04 ` Yu Zhang (Yuriy)
2025-01-15 13:03 ` Jose Ignacio Tornos Martinez
2025-01-16 0:31 ` Jeff Johnson
2025-02-06 7:46 ` Yu Zhang (Yuriy)
2025-02-06 20:20 ` Jeff Johnson
2025-02-07 2:01 ` Yu Zhang (Yuriy)
2025-04-02 12:23 ` Yu Zhang (Yuriy)
2024-12-09 11:23 ` Janusz Dziedzic
2024-12-10 2:32 ` Yu Zhang (Yuriy)
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=20241202091858.200773-1-jtornosm@redhat.com \
--to=jtornosm@redhat.com \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_cjhuang@quicinc.com \
--cc=vbenes@redhat.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