From: Dale Whinham <daleyo@gmail.com>
To: Jeff Johnson <jjohnson@kernel.org>
Cc: "Jérôme de Bretagne" <jerome.debretagne@gmail.com>,
"Dale Whinham" <daleyo@gmail.com>,
linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 8/9 RFC] wifi: ath12k: Add support for disabling rfkill via devicetree
Date: Mon, 14 Jul 2025 18:35:44 +0100 [thread overview]
Message-ID: <20250714173554.14223-9-daleyo@gmail.com> (raw)
In-Reply-To: <20250714173554.14223-1-daleyo@gmail.com>
Some devices (e.g. Microsoft Surface Pro 11) indicate that the rfkill
feature should be disabled by means of an ACPI bitflag.
If ACPI is not being used (i.e. booting using a devicetree) then this
property will not be read and therefore rfkill may be enabled and
the ath12k will be hard-blocked with no way to disable it.
Add a devicetree property that allows us to disable the rfkill feature.
Tested-by: Jérôme de Bretagne <jerome.debretagne@gmail.com>
Signed-off-by: Dale Whinham <daleyo@gmail.com>
---
drivers/net/wireless/ath/ath12k/core.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/net/wireless/ath/ath12k/core.c b/drivers/net/wireless/ath/ath12k/core.c
index 0b2dec081c6e..42a1d384457b 100644
--- a/drivers/net/wireless/ath/ath12k/core.c
+++ b/drivers/net/wireless/ath/ath12k/core.c
@@ -43,6 +43,9 @@ static int ath12k_core_rfkill_config(struct ath12k_base *ab)
if (ath12k_acpi_get_disable_rfkill(ab))
return 0;
+ if (of_property_read_bool(ab->dev->of_node, "disable-rfkill"))
+ return 0;
+
for (i = 0; i < ab->num_radios; i++) {
ar = ab->pdevs[i].ar;
--
2.50.1
next prev parent reply other threads:[~2025-07-14 17:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-14 17:35 [PATCH 0/9] Microsoft Surface Pro 11 support Dale Whinham
2025-07-14 17:35 ` [PATCH 1/9] dt-bindings: arm: qcom: Document Microsoft Surface Pro 11 Dale Whinham
2025-07-15 3:58 ` Rob Herring (Arm)
2025-07-14 17:35 ` [PATCH 2/9] dt-bindings: display: panel: samsung,atna30dw01: document ATNA30DW01 Dale Whinham
2025-07-14 17:41 ` Doug Anderson
2025-07-15 3:58 ` Rob Herring (Arm)
2025-07-15 17:26 ` Doug Anderson
2025-07-14 17:35 ` [PATCH 3/9] firmware: qcom: scm: allow QSEECOM on Surface Pro 11 Dale Whinham
2025-07-14 17:35 ` [PATCH 4/9] platform/surface: aggregator_registry: Add " Dale Whinham
2025-07-15 22:24 ` Maximilian Luz
2025-07-14 17:35 ` [PATCH 5/9] arm64: dts: qcom: Add support for " Dale Whinham
2025-07-14 17:35 ` [PATCH 6/9] drm/msm/dp: Work around bogus maximum link rate Dale Whinham
2025-07-14 19:50 ` Rob Clark
2025-07-15 22:52 ` Jérôme de Bretagne
2025-07-17 2:21 ` Xilin Wu
2025-07-17 20:27 ` Jérôme de Bretagne
2025-07-17 21:10 ` Konrad Dybcio
2025-07-17 21:36 ` Jérôme de Bretagne
2025-07-18 10:52 ` Dmitry Baryshkov
2025-07-18 18:26 ` Jérôme de Bretagne
2025-07-18 18:30 ` Dmitry Baryshkov
2025-07-14 17:35 ` [PATCH 7/9 RFC] dt-bindings: wireless: ath12k: Add disable-rfkill property Dale Whinham
2025-07-14 22:33 ` Dmitry Baryshkov
2025-07-14 23:26 ` Jérôme de Bretagne
2025-07-15 4:02 ` Rob Herring
2025-07-14 17:35 ` Dale Whinham [this message]
2025-07-14 17:35 ` [PATCH 9/9 RFC] arm64: dts: qcom: x1e80100-denali: Disable rfkill for wifi0 Dale Whinham
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=20250714173554.14223-9-daleyo@gmail.com \
--to=daleyo@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=jerome.debretagne@gmail.com \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®