[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20260121095055.3683957-1-miaoqing.pan@oss.qualcomm.com>
Date: Wed, 21 Jan 2026 17:50:53 +0800
From: Miaoqing Pan <miaoqing.pan@....qualcomm.com>
To: jjohnson@...nel.org, johannes@...solutions.net, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org
Cc: ath11k@...ts.infradead.org, linux-wireless@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
jonas.gorski@...il.com, krzk@...nel.org,
Miaoqing Pan <miaoqing.pan@....qualcomm.com>
Subject: [PATCH v4 ath-current 0/2] wifi: ath11k: add usecase firmware handling based on device compatible
The 'firmware-name' property was introduced to allow end-users and
integrators to select use-case-specific firmware for the WCN6855.
But for M.2 WLAN chips, there is no suitable DTS node to specify
the 'firmware-name' property. In addition, assigning firmware for
the M.2 PCIe interface causes chips that do not use use-case-specific
firmware to fail. Therefore, abandoning the approach of specifying
firmware in DTS. As an alternative, propose a static lookup table
mapping device compatible to firmware names.
---
v2:
- Drops `firmware-name` from completely.
- Updates the commit message to clearly state that the property is
obsolete and the change is ABI-breaking but safe for upstream.
v3:
- Deprecate 'firmware-name' property instead of obsolete.
- Keep the ABI backwards compatible.
v4:
- Use of_machine_is_compatible() to simplify the code.
- Add back Acked-by tag.
---
Miaoqing Pan (2):
wifi: ath11k: add usecase firmware handling based on device compatible
dt-bindings: net: wireless: ath11k-pci: deprecate 'firmware-name'
property
.../net/wireless/qcom,ath11k-pci.yaml | 1 +
drivers/net/wireless/ath/ath11k/core.c | 27 +++++++++++++++++++
drivers/net/wireless/ath/ath11k/core.h | 4 +++
3 files changed, 32 insertions(+)
base-commit: d8e1f4a193101a72235416f189b01131a57e26e9
--
2.34.1
Powered by blists - more mailing lists