The firmware-name property was introduced to allow end-users and
integrators to select usecase specific firmware for the WCN6855.
However, specifying firmware for an M.2 WLAN module in the Device
Tree is not appropriate. Instead, this functionality will be handled
within the ath11k driver.
Signed-off-by: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
---
.../devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml
index e34d42a30192..0162e365798b 100644
--- a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml
+++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml
@@ -37,6 +37,7 @@ properties:
firmware-name:
maxItems: 1
+ deprecated: true
description:
If present, a board or platform specific string used to lookup
usecase-specific firmware files for the device.
--
2.34.1On 12/3/2025 11:11 PM, Miaoqing Pan wrote: > The firmware-name property was introduced to allow end-users and > integrators to select usecase specific firmware for the WCN6855. > However, specifying firmware for an M.2 WLAN module in the Device > Tree is not appropriate. Instead, this functionality will be handled > within the ath11k driver. > > Signed-off-by: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com> > --- > .../devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml > index e34d42a30192..0162e365798b 100644 > --- a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml > +++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml > @@ -37,6 +37,7 @@ properties: > > firmware-name: > maxItems: 1 > + deprecated: true > description: > If present, a board or platform specific string used to lookup > usecase-specific firmware files for the device. The driver patch completely removes support for this, so is this really considered deprecated? Or should this actually be considered obsolete and completely removed? Do any DTS files actually reference this? /jeff
On 12/12/2025 12:44 AM, Jeff Johnson wrote: > On 12/3/2025 11:11 PM, Miaoqing Pan wrote: >> The firmware-name property was introduced to allow end-users and >> integrators to select usecase specific firmware for the WCN6855. >> However, specifying firmware for an M.2 WLAN module in the Device >> Tree is not appropriate. Instead, this functionality will be handled >> within the ath11k driver. >> >> Signed-off-by: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com> >> --- >> .../devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml >> index e34d42a30192..0162e365798b 100644 >> --- a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml >> +++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml >> @@ -37,6 +37,7 @@ properties: >> >> firmware-name: >> maxItems: 1 >> + deprecated: true >> description: >> If present, a board or platform specific string used to lookup >> usecase-specific firmware files for the device. > > The driver patch completely removes support for this, so is this really > considered deprecated? Or should this actually be considered obsolete and > completely removed? > > Do any DTS files actually reference this? > > /jeff You are correct — since the driver has already removed all support for `firmware-name`, marking it as `deprecated` is misleading. The proper status should be `obsolete`, and the binding should reflect that this property is no longer supported. Regarding DTS usage: no upstream Device Tree files currently reference `firmware-name`.
On 11/12/2025 17:44, Jeff Johnson wrote: > On 12/3/2025 11:11 PM, Miaoqing Pan wrote: >> The firmware-name property was introduced to allow end-users and >> integrators to select usecase specific firmware for the WCN6855. >> However, specifying firmware for an M.2 WLAN module in the Device >> Tree is not appropriate. Instead, this functionality will be handled >> within the ath11k driver. >> >> Signed-off-by: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com> >> --- >> .../devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml >> index e34d42a30192..0162e365798b 100644 >> --- a/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml >> +++ b/Documentation/devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml >> @@ -37,6 +37,7 @@ properties: >> >> firmware-name: >> maxItems: 1 >> + deprecated: true >> description: >> If present, a board or platform specific string used to lookup >> usecase-specific firmware files for the device. > > The driver patch completely removes support for this, so is this really > considered deprecated? Or should this actually be considered obsolete and That's silent ABI break. I will formally NAK the patch. > completely removed? > > Do any DTS files actually reference this? > > /jeff Best regards, Krzysztof
On Thu, 04 Dec 2025 15:11:00 +0800, Miaoqing Pan wrote: > The firmware-name property was introduced to allow end-users and > integrators to select usecase specific firmware for the WCN6855. > However, specifying firmware for an M.2 WLAN module in the Device > Tree is not appropriate. Instead, this functionality will be handled > within the ath11k driver. > > Signed-off-by: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com> > --- > .../devicetree/bindings/net/wireless/qcom,ath11k-pci.yaml | 1 + > 1 file changed, 1 insertion(+) > Acked-by: Rob Herring (Arm) <robh@kernel.org>
© 2016 - 2025 Red Hat, Inc.