One big Qualcomm Bluetooth schema is hardly manageable: it lists all
possible properties (19 supplies). Split qcom,qcc2072-bt to separate
bindings, so device schema will be easier to read/maintain and list only
relevant properties.
Signed-off-by: Vivek Sahu <vivek.sahu@oss.qualcomm.com>
---
.../net/bluetooth/qcom,qcc2072-bt.yaml | 48 +++++++++++++++++++
1 file changed, 48 insertions(+)
create mode 100644 Documentation/devicetree/bindings/net/bluetooth/qcom,qcc2072-bt.yaml
diff --git a/Documentation/devicetree/bindings/net/bluetooth/qcom,qcc2072-bt.yaml b/Documentation/devicetree/bindings/net/bluetooth/qcom,qcc2072-bt.yaml
new file mode 100644
index 000000000000..48936bb8e91c
--- /dev/null
+++ b/Documentation/devicetree/bindings/net/bluetooth/qcom,qcc2072-bt.yaml
@@ -0,0 +1,48 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/net/bluetooth/qcom,qcc2072-bt.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Qualcomm QCC2072 Bluetooth
+
+maintainers:
+ - Balakrishna Godavarthi <quic_bgodavar@quicinc.com>
+ - Rocky Liao <quic_rjliao@quicinc.com>
+ - Vivek Sahu <vivek.sahu@oss.qualcomm.com>
+
+description:
+ Qualcomm QCC2072 is a UART-based Bluetooth controller.
+
+properties:
+ compatible:
+ enum:
+ - qcom,qcc2072-bt
+
+ enable-gpios:
+ maxItems: 1
+ description: GPIO specifier for the chip interrupt.
+
+required:
+ - compatible
+ - enable-gpios
+
+allOf:
+ - $ref: bluetooth-controller.yaml#
+ - $ref: qcom,bluetooth-common.yaml
+ - $ref: /schemas/serial/serial-peripheral-props.yaml#
+
+unevaluatedProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/gpio/gpio.h>
+ #include <dt-bindings/interrupt-controller/irq.h>
+
+ serial {
+ bluetooth {
+ compatible = "qcom,qcc2072-bt";
+ enable-gpios = <&tlmm 19 IRQ_TYPE_EDGE_FALLING>;
+ max-speed = <3200000>;
+ };
+ };
--
2.34.1On Tue, Feb 17, 2026 at 11:17:30AM +0530, Vivek Sahu wrote: > One big Qualcomm Bluetooth schema is hardly manageable: it lists all > possible properties (19 supplies). Split qcom,qcc2072-bt to separate > bindings, so device schema will be easier to read/maintain and list only > relevant properties. Huh? I do not see any split here and I do not see how this commit msg relates anyhow to what the patch is doing. > > Signed-off-by: Vivek Sahu <vivek.sahu@oss.qualcomm.com> > --- > .../net/bluetooth/qcom,qcc2072-bt.yaml | 48 +++++++++++++++++++ Best regards, Krzysztof
On 2/17/2026 1:21 PM, Krzysztof Kozlowski wrote: > On Tue, Feb 17, 2026 at 11:17:30AM +0530, Vivek Sahu wrote: >> One big Qualcomm Bluetooth schema is hardly manageable: it lists all >> possible properties (19 supplies). Split qcom,qcc2072-bt to separate >> bindings, so device schema will be easier to read/maintain and list only >> relevant properties. > > Huh? I do not see any split here and I do not see how this commit msg > relates anyhow to what the patch is doing. Let me re-write the commit message with more clear information about the patch. >> >> Signed-off-by: Vivek Sahu <vivek.sahu@oss.qualcomm.com> >> --- >> .../net/bluetooth/qcom,qcc2072-bt.yaml | 48 +++++++++++++++++++ > > > Best regards, > Krzysztof >
On Tue, Feb 17, 2026 at 11:17:30AM +0530, Vivek Sahu wrote: > One big Qualcomm Bluetooth schema is hardly manageable: it lists all > possible properties (19 supplies). Split qcom,qcc2072-bt to separate > bindings, so device schema will be easier to read/maintain and list only > relevant properties. How is it relevant to the commit? You are not splitting anything. You are adding bindings for the new hardware. > > Signed-off-by: Vivek Sahu <vivek.sahu@oss.qualcomm.com> > --- > .../net/bluetooth/qcom,qcc2072-bt.yaml | 48 +++++++++++++++++++ > 1 file changed, 48 insertions(+) > create mode 100644 Documentation/devicetree/bindings/net/bluetooth/qcom,qcc2072-bt.yaml > -- With best wishes Dmitry
On 2/17/2026 12:04 PM, Dmitry Baryshkov wrote: > On Tue, Feb 17, 2026 at 11:17:30AM +0530, Vivek Sahu wrote: >> One big Qualcomm Bluetooth schema is hardly manageable: it lists all >> possible properties (19 supplies). Split qcom,qcc2072-bt to separate >> bindings, so device schema will be easier to read/maintain and list only >> relevant properties. > > How is it relevant to the commit? You are not splitting anything. You > are adding bindings for the new hardware. This commit is added on top of split schema where for each chip set there is separate binding yaml file instead of following up traditional method of updating qualcomm-bluetooth.yaml > >> >> Signed-off-by: Vivek Sahu <vivek.sahu@oss.qualcomm.com> >> --- >> .../net/bluetooth/qcom,qcc2072-bt.yaml | 48 +++++++++++++++++++ >> 1 file changed, 48 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/net/bluetooth/qcom,qcc2072-bt.yaml >> >
On Tue, Feb 17, 2026 at 01:11:05PM +0530, Vivek Sahu wrote: > > > On 2/17/2026 12:04 PM, Dmitry Baryshkov wrote: > > On Tue, Feb 17, 2026 at 11:17:30AM +0530, Vivek Sahu wrote: > > > One big Qualcomm Bluetooth schema is hardly manageable: it lists all > > > possible properties (19 supplies). Split qcom,qcc2072-bt to separate > > > bindings, so device schema will be easier to read/maintain and list only > > > relevant properties. > > > > How is it relevant to the commit? You are not splitting anything. You > > are adding bindings for the new hardware. > This commit is added on top of split schema where for each chip set there is > separate binding yaml file instead of following up traditional > method of updating qualcomm-bluetooth.yaml What does your commit message describe? What are you splitting? > > > > > > > > Signed-off-by: Vivek Sahu <vivek.sahu@oss.qualcomm.com> > > > --- > > > .../net/bluetooth/qcom,qcc2072-bt.yaml | 48 +++++++++++++++++++ > > > 1 file changed, 48 insertions(+) > > > create mode 100644 Documentation/devicetree/bindings/net/bluetooth/qcom,qcc2072-bt.yaml > > > > > > -- With best wishes Dmitry
On 2/17/2026 1:43 PM, Dmitry Baryshkov wrote: > On Tue, Feb 17, 2026 at 01:11:05PM +0530, Vivek Sahu wrote: >> >> >> On 2/17/2026 12:04 PM, Dmitry Baryshkov wrote: >>> On Tue, Feb 17, 2026 at 11:17:30AM +0530, Vivek Sahu wrote: >>>> One big Qualcomm Bluetooth schema is hardly manageable: it lists all >>>> possible properties (19 supplies). Split qcom,qcc2072-bt to separate >>>> bindings, so device schema will be easier to read/maintain and list only >>>> relevant properties. >>> >>> How is it relevant to the commit? You are not splitting anything. You >>> are adding bindings for the new hardware. >> This commit is added on top of split schema where for each chip set there is >> separate binding yaml file instead of following up traditional >> method of updating qualcomm-bluetooth.yaml > > What does your commit message describe? What are you splitting? > The commit is about adding a binding for new chipset QCC2072 which is a WiFi/BT connectivity chip. It requires different firmware, so document it as a new compatible string. Seems like slit to separate schema is confusing sentence for this commit. I'll correct it in new patch set. >>> >>>> >>>> Signed-off-by: Vivek Sahu <vivek.sahu@oss.qualcomm.com> >>>> --- >>>> .../net/bluetooth/qcom,qcc2072-bt.yaml | 48 +++++++++++++++++++ >>>> 1 file changed, 48 insertions(+) >>>> create mode 100644 Documentation/devicetree/bindings/net/bluetooth/qcom,qcc2072-bt.yaml >>>> >>> >> >
On 17/02/2026 09:19, Vivek Sahu wrote: > > > On 2/17/2026 1:43 PM, Dmitry Baryshkov wrote: >> On Tue, Feb 17, 2026 at 01:11:05PM +0530, Vivek Sahu wrote: >>> >>> >>> On 2/17/2026 12:04 PM, Dmitry Baryshkov wrote: >>>> On Tue, Feb 17, 2026 at 11:17:30AM +0530, Vivek Sahu wrote: >>>>> One big Qualcomm Bluetooth schema is hardly manageable: it lists all >>>>> possible properties (19 supplies). Split qcom,qcc2072-bt to separate >>>>> bindings, so device schema will be easier to read/maintain and list only >>>>> relevant properties. >>>> >>>> How is it relevant to the commit? You are not splitting anything. You >>>> are adding bindings for the new hardware. >>> This commit is added on top of split schema where for each chip set there is >>> separate binding yaml file instead of following up traditional >>> method of updating qualcomm-bluetooth.yaml >> >> What does your commit message describe? What are you splitting? >> > The commit is about adding a binding for new chipset QCC2072 which is a > WiFi/BT connectivity chip. It requires different firmware, so document > it as a new compatible string. > Seems like slit to separate schema is confusing sentence for this > commit. I'll correct it in new patch set. No, it is not confusing. It is just false, a lie. You are not doing what your commit message said. Best regards, Krzysztof
© 2016 - 2026 Red Hat, Inc.