From: Cheng Jiang <quic_chejiang@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: 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>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
"Balakrishna Godavarthi" <quic_bgodavar@quicinc.com>,
Rocky Liao <quic_rjliao@quicinc.com>, <quic_zijuhu@quicinc.com>,
<linux-bluetooth@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<quic_mohamull@quicinc.com>
Subject: Re: [PATCH v2 2/4] dt-bindings: bluetooth: Add qca6698 compatible string
Date: Thu, 21 Nov 2024 12:12:16 +0800 [thread overview]
Message-ID: <44932c08-000f-4e6c-89b3-d7556a0a7a88@quicinc.com> (raw)
In-Reply-To: <smwxrjvdvyxw6tknucl6fb5jpjau2q4jcyjxpunbtt5ep6xsr4@ztuyfkrwgxoo>
Hi Dmitry,
On 11/20/2024 6:44 PM, Dmitry Baryshkov wrote:
> On Wed, Nov 20, 2024 at 05:54:26PM +0800, Cheng Jiang wrote:
>> Add QCA6698 qcom,qca6698-bt compatible strings.
>
> Why? Is it the same chip as WCN6855 or a different chip? Is it
> completely compatible?
>
They are different chips. But it's compatible with WCN6855.
>>
>> Signed-off-by: Cheng Jiang <quic_chejiang@quicinc.com>
>> ---
>> .../devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml b/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml
>> index 9019fe7bcdc6..527f947289af 100644
>> --- a/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml
>> +++ b/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml
>> @@ -18,6 +18,7 @@ properties:
>> enum:
>> - qcom,qca2066-bt
>> - qcom,qca6174-bt
>> + - qcom,qca6698-bt
>> - qcom,qca9377-bt
>> - qcom,wcn3988-bt
>> - qcom,wcn3990-bt
>> @@ -175,6 +176,7 @@ allOf:
>> compatible:
>> contains:
>> enum:
>> + - qcom,qca6698-bt
>> - qcom,wcn6855-bt
>> then:
>> required:
>> --
>> 2.25.1
>>
>
next prev parent reply other threads:[~2024-11-21 4:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 9:54 [PATCH v1 0/4] Add qcom,product-variant properties in Qualcomm Cheng Jiang
2024-11-20 9:54 ` [PATCH v2 1/4] dt-bindings: bluetooth: add 'qcom,product-variant' Cheng Jiang
2024-11-20 10:43 ` Dmitry Baryshkov
2024-11-21 4:02 ` Cheng Jiang
2024-11-21 4:38 ` Dmitry Baryshkov
2024-11-21 4:44 ` Cheng Jiang
2024-11-30 3:47 ` Cheng Jiang (IOE)
2024-11-30 8:24 ` Dmitry Baryshkov
2024-12-02 2:22 ` Cheng Jiang (IOE)
2024-12-02 11:38 ` Dmitry Baryshkov
2024-12-02 14:25 ` Cheng Jiang (IOE)
2024-12-02 15:14 ` Dmitry Baryshkov
2024-12-03 3:04 ` Cheng Jiang (IOE)
2024-11-20 16:47 ` Krzysztof Kozlowski
2024-11-21 4:06 ` Cheng Jiang
2024-11-21 7:49 ` Krzysztof Kozlowski
2024-11-21 15:53 ` Cheng Jiang (IOE)
2024-11-22 12:49 ` Konrad Dybcio
2024-11-22 13:08 ` Konrad Dybcio
2024-11-20 9:54 ` [PATCH v2 2/4] dt-bindings: bluetooth: Add qca6698 compatible string Cheng Jiang
2024-11-20 10:44 ` Dmitry Baryshkov
2024-11-21 4:12 ` Cheng Jiang [this message]
2024-11-21 15:57 ` Krzysztof Kozlowski
2024-11-21 16:28 ` Dmitry Baryshkov
2024-11-22 1:55 ` Cheng Jiang (IOE)
2024-11-22 2:16 ` quic_zijuhu
2024-11-22 8:01 ` Dmitry Baryshkov
2024-11-20 16:47 ` Krzysztof Kozlowski
2024-11-20 9:54 ` [PATCH v2 3/4] arm64: dts: qcom: sa8775p-ride: update BT nodes Cheng Jiang
2024-11-20 10:44 ` Dmitry Baryshkov
2024-11-20 16:47 ` Krzysztof Kozlowski
2024-11-20 9:54 ` [PATCH v2 4/4] Bluetooth: hci_qca: add qcom,product-variant properties Cheng Jiang
2024-11-20 10:57 ` Dmitry Baryshkov
2024-11-21 4:40 ` Cheng Jiang
2024-11-21 18:41 ` Dmitry Baryshkov
2024-11-22 7:20 ` Cheng Jiang (IOE)
2024-11-20 10:59 ` neil.armstrong
2024-11-21 4:48 ` Cheng Jiang
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=44932c08-000f-4e6c-89b3-d7556a0a7a88@quicinc.com \
--to=quic_chejiang@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--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_mohamull@quicinc.com \
--cc=quic_rjliao@quicinc.com \
--cc=quic_zijuhu@quicinc.com \
--cc=robh@kernel.org \
/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