Re: [PATCH 1/2] DT: add bindings for QCC2072 Add DT compatible string "qcom,qcc2072-bt" to yaml file.

[Vivek Sahu]

On 1/20/2026 3:38 PM, Vivek Sahu wrote:
> > ________________________________
> > From: Paul Menzel <pmenzel@xxxxxxxxxxxxx>
> > Sent: 17 December 2025 19:44
> > To: Vivek Sahu <vivesahu@xxxxxxxxxxxxxxxx>
> > Cc: Marcel Holtmann <marcel@xxxxxxxxxxxx>; Luiz Augusto von Dentz 
> > <luiz.dentz@xxxxxxxxx>; Rob Herring <robh@xxxxxxxxxx>; Krzysztof 
> > Kozlowski <krzk+dt@xxxxxxxxxx>; Conor Dooley <conor+dt@xxxxxxxxxx>; 
> > Bartosz Golaszewski <brgl@xxxxxxxx>; Balakrishna Godavarthi (QUIC) 
> > <quic_bgodavar@xxxxxxxxxxx>; Rocky Liao (QUIC) 
> > <quic_rjliao@xxxxxxxxxxx>; Mohammed Sameer Mulla (QUIC) 
> > <quic_mohamull@xxxxxxxxxxx>; Harish Bandi (QUIC) 
> > <quic_hbandi@xxxxxxxxxxx>; linux-bluetooth@xxxxxxxxxxxxxxx 
> > <linux-bluetooth@xxxxxxxxxxxxxxx>; devicetree@xxxxxxxxxxxxxxx 
> > <devicetree@xxxxxxxxxxxxxxx>; linux-kernel@xxxxxxxxxxxxxxx 
> > <linux-kernel@xxxxxxxxxxxxxxx>; linux-arm-msm@xxxxxxxxxxxxxxx 
> > <linux-arm-msm@xxxxxxxxxxxxxxx>
> > Subject: Re: [PATCH 1/2] DT: add bindings for QCC2072 Add DT 
> > compatible string "qcom,qcc2072-bt" to yaml file.
> >
> > WARNING: This email originated from outside of Qualcomm. Please be 
> > wary of any links or attachments, and do not enable macros.
> >
> > Dear Vivek,
> >
> >
> > Thank you for your patch. The formatting is off, and the summary/title
> > (subject) has two statements – look yourself in the archive [1]. Also
> > the prefix seems wrong.
> >
> > Am 17.12.25 um 12:28 schrieb Vivek Kumar Sahu:
> > > Signed-off-by: Vivek Kumar Sahu <vivesahu@xxxxxxxxxxxxxxxx>
> > Please elaborate by giving more context, why it is compatible, and I’d
> > like to see how you tested this.
>
> The compatible string "qcom,qcc2072-bt" is defined in target dtsi file 
> and it was tested on the hardware. The corresponding target specific 
> dtsi file is currently merged in downstream.
Please let me know if above statement gets you the answer of your question.
> > > ---
> > > .../devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml | 1 +
> > >    1 file changed, 1 insertion(+)
> > >
> > > diff --git 
> > > a/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml 
> > > b/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml 
> > >
> > > index 6353a336f382..197248d6f7b8 100644
> > > --- 
> > > a/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml
> > > +++ 
> > > b/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml
> > > @@ -28,6 +28,7 @@ properties:
> > >          - qcom,wcn6750-bt
> > >          - qcom,wcn6855-bt
> > >          - qcom,wcn7850-bt
> > > +      - qcom,qcc2072-bt
> > Lacking more lines, I am not certain, but I maybe this should be sorted.
> I'll address it in next patch of this commit.
I just checked that "qca_btsoc_type" enum contains all the soc type 
which need to be enabled

for BT enablement on the target device. There are few places where logic 
of framing packets transferring

between SoC  and Host depends on the which generation of the chip it is, 
refer api "qca_read_soc_version".

Do you still suggest to sort it here ?

> > >      enable-gpios:
> > >        maxItems: 1
> >
> > Kind regards,
> >
> > Paul
> >
> >
> > [1]:
> > https://lore.kernel.org/all/20251217112850.520572-1-vivesahu@xxxxxxxxxxxxxxxx/