From: Krzysztof Kozlowski <krzk@kernel.org>
To: Cheng Jiang <quic_chejiang@quicinc.com>,
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
Cc: 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 1/4] dt-bindings: bluetooth: add 'qcom,product-variant'
Date: Wed, 20 Nov 2024 17:47:06 +0100 [thread overview]
Message-ID: <c8ae761a-732c-4def-ac6e-5e1b16a21ada@kernel.org> (raw)
In-Reply-To: <20241120095428.1122935-2-quic_chejiang@quicinc.com>
On 20/11/2024 10:54, Cheng Jiang wrote:
> Several Qualcomm projects will use the same Bluetooth chip, each
> focusing on different features. For instance, consumer projects
> prioritize the A2DP SRC feature, while IoT projects focus on the A2DP
> SINK feature, which may have more optimizations for coexistence when
> acting as a SINK. Due to the patch size, it is not feasible to include
> all features in a single firmware.
>
> Therefore, the 'product-variant' devicetree property is used to provide
> product information for the Bluetooth driver to load the appropriate
> firmware.
>
> If this property is not defined, the default firmware will be loaded,
> ensuring there are no backward compatibility issues with older
> devicetrees.
>
> The product-variant defines like this:
> 0 - 15 (16 bits) are product line specific definitions
> 16 - 23 (8 bits) are for the product line.
> 24 - 31 (8 bits) are reserved for future use, 0 currently
>
> |---------------------------------------------------------------------|
> | 32 Bits |
> |---------------------------------------------------------------------|
> | 31 - 24 (bits) | 23 - 16 (bits) | 15 - 0 (16 bits) |
> |---------------------------------------------------------------------|
> | Reserved | 0: default | 0: default |
> | | 1: CE | |
> | | 2: IoT | |
> | | 3: Auto | |
> | | 4: Reserved | |
> |---------------------------------------------------------------------|
>
> Signed-off-by: Cheng Jiang <quic_chejiang@quicinc.com>
> ---
> .../bindings/net/bluetooth/qualcomm-bluetooth.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml b/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml
> index 7bb68311c609..9019fe7bcdc6 100644
> --- a/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml
> +++ b/Documentation/devicetree/bindings/net/bluetooth/qualcomm-bluetooth.yaml
> @@ -110,6 +110,12 @@ properties:
> description:
> boot firmware is incorrectly passing the address in big-endian order
>
> + qcom,product-variant:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description:
> + specify the product information for driver to load the appropriate firmware
Nah, you have firmware-name for this.
> +
> +
No clue why two blank lines...
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-11-20 16:47 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 [this message]
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
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=c8ae761a-732c-4def-ac6e-5e1b16a21ada@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.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_chejiang@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