From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vivek Sahu <vivek.sahu@oss.qualcomm.com>,
Bartosz Golaszewski <brgl@kernel.org>,
Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Balakrishna Godavarthi <quic_bgodavar@quicinc.com>,
Rocky Liao <quic_rjliao@quicinc.com>
Cc: quic_mohamull@quicinc.com, quic_hbandi@quicinc.com,
janaki.thota@oss.qualcomm.com, linux-arm-msm@vger.kernel.org,
linux-bluetooth@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] dt-bindings: bluetooth: qcom,qcc2072-bt: add bindings for QCC2072
Date: Wed, 18 Feb 2026 12:53:36 +0100 [thread overview]
Message-ID: <af950713-4a0d-43ec-8000-3400f546acbd@kernel.org> (raw)
In-Reply-To: <20260218114955.3970974-2-vivek.sahu@oss.qualcomm.com>
On 18/02/2026 12:49, Vivek Sahu wrote:
> QCC2072 is a WiFi/BT connectivity radios which exposes
> UART as an interface for Bluetooth part.
> It requires different configuartions and firmware, so
different than what?
Also typo configurations.
> document it as a new compatible string.
Please wrap commit message according to Linux coding style / submission
process (neither too early nor over the limit):
https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
>
> Signed-off-by: Vivek Sahu <vivek.sahu@oss.qualcomm.com>
> ---
> .../net/bluetooth/qcom,qcc2072-bt.yaml | 47 +++++++++++++++++++
> 1 file changed, 47 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..7b27c2c651fa
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/net/bluetooth/qcom,qcc2072-bt.yaml
> @@ -0,0 +1,47 @@
> +# 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>
> +
> +description:
> + Qualcomm QCC2072 is a UART-based Bluetooth controller.
> +
> +properties:
> + compatible:
> + enum:
> + - qcom,qcc2072-bt
> +
Where are clocks?
Where are supplies?
> + enable-gpios:
> + maxItems: 1
> + description: GPIO specifier for the chip interrupt.
Interrupt? No, it cannot be interrupt. This can be only enable pin and
then description is redundant. Look at other bindings.
Looks like matching QCA2066, except missing clocks, or like other QCA
devices with proper supplies.
I don't believe that Bluetooth device works without power.
> +
> +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>;
No firmware?
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-18 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 11:49 [PATCH v5 0/2] Cover letter QCC2072 enablement Vivek Sahu
2026-02-18 11:49 ` [PATCH v5 1/2] dt-bindings: bluetooth: qcom,qcc2072-bt: add bindings for QCC2072 Vivek Sahu
2026-02-18 11:53 ` Krzysztof Kozlowski [this message]
2026-02-20 12:05 ` Vivek Sahu
2026-02-20 12:32 ` Krzysztof Kozlowski
2026-02-18 13:12 ` Cover letter QCC2072 enablement bluez.test.bot
2026-02-18 11:49 ` [PATCH v5 2/2] Bluetooth: qca: add QCC2072 support Vivek Sahu
2026-02-18 13:57 ` Dmitry Baryshkov
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=af950713-4a0d-43ec-8000-3400f546acbd@kernel.org \
--to=krzk@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=janaki.thota@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=quic_bgodavar@quicinc.com \
--cc=quic_hbandi@quicinc.com \
--cc=quic_mohamull@quicinc.com \
--cc=quic_rjliao@quicinc.com \
--cc=robh@kernel.org \
--cc=vivek.sahu@oss.qualcomm.com \
/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