From nobody Mon Feb 9 02:51:05 2026 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6CD152F9D85; Thu, 18 Dec 2025 22:22:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766096534; cv=none; b=ckUCK+1ebjaO2FAje2yNDmQNolSkjsDlWANaSSjJ9RQbCWibmfcicwndvJZoNzylzvhLwpG2l9e/tEnMHnjxb/l+fQAAo8KESxhVVlbTatvqzJG/qXsBO/nSVLf77vqICdrbb68jT/mbdINTpoVEW71vTk7RSd5p5QP2MTNVdlg= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766096534; c=relaxed/simple; bh=C/ueUWFjCyD/VD4TdJXJVaQRqT2VnOEHgebnD6XjxSI=; h=From:Date:Subject:MIME-Version:Content-Type:Message-Id:References: In-Reply-To:To:Cc; b=qZwnkoQlfBB79JYA85pwk6QN9lMnGaT1OVsIqQLaBnHtHcXt303m66/5Qc2Mpypf+mJ0X4raCVBB7LiATMcRrC1gwGQ/57QZwIr/FNmsi6BQgmBEHJ+1FtieOnKjpkFHmInQ/okYutOTEAVhV71Qatm59USfMnoR8qKEuGqzZjc= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=KTRj7JIp; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="KTRj7JIp" Received: by smtp.kernel.org (Postfix) with ESMTPS id 01625C2BCB1; Thu, 18 Dec 2025 22:22:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1766096534; bh=C/ueUWFjCyD/VD4TdJXJVaQRqT2VnOEHgebnD6XjxSI=; h=From:Date:Subject:References:In-Reply-To:To:Cc:Reply-To:From; b=KTRj7JIpKmE1PPDUUHXPOPSMVHucq1I9S79x1nSEY6RP8VzTez7yHmgQ1/5HzUuqQ FMnkSmosCbPi2Cq14zuZBETeXjzKV1PjSqpLxIBFtwPpb2AvTE5Vzgz1tUwdQHkMwf uRohtnw6MB9lVixxc/JEFtrcIw6nNsowoR/6a/31BOGcoqrG2LVLoJKRKLa3fo4cfX ZPL9DMD0bXmISjryX46ktSVHjxEcL+VibuaG1UxfTKl8dNdHb9eJBXp20mw8ij1Lan B+zunLaS6Xj9vdlNC+GGXH8bGQkZGMrpi1n9Yl3AEi7/Gt/hblWuNINexgxuxZ/YoV GuvYFYM40r/+A== Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id EDCAAD711C8; Thu, 18 Dec 2025 22:22:13 +0000 (UTC) From: =?utf-8?q?J=C3=A9r=C3=B4me_de_Bretagne_via_B4_Relay?= Date: Thu, 18 Dec 2025 23:22:12 +0100 Subject: [PATCH v4 6/6] wifi: ath12k: Add support for disabling rfkill via devicetree Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <20251218-surface-sp11-for-next-v4-6-7bcf83c1504a@gmail.com> References: <20251218-surface-sp11-for-next-v4-0-7bcf83c1504a@gmail.com> In-Reply-To: <20251218-surface-sp11-for-next-v4-0-7bcf83c1504a@gmail.com> To: Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Johannes Berg , Lorenzo Bianconi , Maximilian Luz , Hans de Goede , =?utf-8?q?Ilpo_J=C3=A4rvinen?= , Jeff Johnson Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org, platform-driver-x86@vger.kernel.org, ath12k@lists.infradead.org, Dale Whinham , =?utf-8?q?J=C3=A9r=C3=B4me_de_Bretagne?= X-Mailer: b4 0.14.2 X-Developer-Signature: v=1; a=ed25519-sha256; t=1766096532; l=1265; i=jerome.debretagne@gmail.com; s=20251217; h=from:subject:message-id; bh=mcMjGRXAT6QkIO3PWrqFYRB9BASEzAi+bYp6SS6IoLc=; b=RvVTMjLt69VKME0qck0aSGBZHhTiJB7g5TGhGTiFfRV1Zn3JKB+k59xK71oilLW17JqRP2nS9 GCFTHv10WNTBsGRyxaoG6hYwUDYgJbLXd3qhZL5/WIDKtTeFprXBY0t X-Developer-Key: i=jerome.debretagne@gmail.com; a=ed25519; pk=DcPD9n3oDMsPkt+12tU96swmGb5H86cxt+yiEVcUEGk= X-Endpoint-Received: by B4 Relay for jerome.debretagne@gmail.com/20251217 with auth_id=580 X-Original-From: =?utf-8?q?J=C3=A9r=C3=B4me_de_Bretagne?= Reply-To: jerome.debretagne@gmail.com From: Dale Whinham 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. Signed-off-by: Dale Whinham Tested-by: J=C3=A9r=C3=B4me de Bretagne Signed-off-by: J=C3=A9r=C3=B4me de Bretagne --- 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 cc352eef1939937ce902bee2fbd9737ca3ab5993..e10073bb975cfd2e9ee418edcc4= 9d0d51cf93de1 100644 --- a/drivers/net/wireless/ath/ath12k/core.c +++ b/drivers/net/wireless/ath/ath12k/core.c @@ -77,6 +77,9 @@ static int ath12k_core_rfkill_config(struct ath12k_base *= ab) if (ath12k_acpi_get_disable_rfkill(ab)) return 0; =20 + if (of_property_read_bool(ab->dev->of_node, "disable-rfkill")) + return 0; + for (i =3D 0; i < ab->num_radios; i++) { ar =3D ab->pdevs[i].ar; =20 --=20 2.47.3