From: Cheng Jiang <quic_chejiang@quicinc.com>
To: 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>, <quic_chejiang@quicinc.com>
Subject: [PATCH v1 0/4] Add qcom,product-variant properties in Qualcomm
Date: Wed, 20 Nov 2024 17:54:24 +0800 [thread overview]
Message-ID: <20241120095428.1122935-1-quic_chejiang@quicinc.com> (raw)
Add a new property in qualcom bluetooth dts to identify the product
information, so the driver can load the proper firmware.
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. 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.
The driver will parse 'product-variant' to load firmware from different
directories. If it's not defined in dts, the default firmware will be
loaded, which is compatible with the existing implementaion.
Cheng Jiang (4):
dt-bindings: bluetooth: add 'qcom,product-variant'
dt-bindings: bluetooth: Add qca6698 compatible string
arm64: dts: qcom: sa8775p-ride: update BT nodes
Bluetooth: hci_qca: add qcom,product-variant properties
.../net/bluetooth/qualcomm-bluetooth.yaml | 8 +
arch/arm64/boot/dts/qcom/sa8775p-ride.dtsi | 3 +-
drivers/bluetooth/btqca.c | 142 ++++++++++++++----
drivers/bluetooth/btqca.h | 11 +-
drivers/bluetooth/hci_qca.c | 73 +++++----
5 files changed, 174 insertions(+), 63 deletions(-)
base-commit: 6fb2fa9805c501d9ade047fc511961f3273cdcb5
--
2.25.1
next reply other threads:[~2024-11-20 9:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 9:54 Cheng Jiang [this message]
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-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-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 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-20 10:59 ` neil.armstrong
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=20241120095428.1122935-1-quic_chejiang@quicinc.com \
--to=quic_chejiang@quicinc.com \
--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_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