From: Krzysztof Kozlowski <krzk@kernel.org>
To: Felix Kaechele <felix@kaechele.ca>,
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>, Kalle Valo <kvalo@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Balakrishna Godavarthi <quic_bgodavar@quicinc.com>,
Rocky Liao <quic_rjliao@quicinc.com>
Cc: linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
linux-mmc@vger.kernel.org
Subject: Re: [PATCH 4/4] Bluetooth: hci_qca: add compatible for QCA9379
Date: Mon, 5 Aug 2024 07:31:39 +0200 [thread overview]
Message-ID: <88d08de1-ce0f-4fe2-975b-29e451f5659e@kernel.org> (raw)
In-Reply-To: <20240805040131.450412-5-felix@kaechele.ca>
On 05/08/2024 06:01, Felix Kaechele wrote:
> The QCA9379 (Naples) is a WiFi and Bluetooth SoC in the QCA6174 (Rome)
> family. As such it is supported by this driver.
>
> According to the naming format defined in the code, the driver will
> request the following firmware files for a QCA9379-3:
> - nvm_00150100.bin
> - rampatch_00150100.bin
>
> Signed-off-by: Felix Kaechele <felix@kaechele.ca>
> ---
> drivers/bluetooth/hci_qca.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/bluetooth/hci_qca.c b/drivers/bluetooth/hci_qca.c
> index ca6466676902..06895bafd3b6 100644
> --- a/drivers/bluetooth/hci_qca.c
> +++ b/drivers/bluetooth/hci_qca.c
> @@ -2690,6 +2690,7 @@ static const struct of_device_id qca_bluetooth_of_match[] = {
> { .compatible = "qcom,qca6174-bt" },
> { .compatible = "qcom,qca6390-bt", .data = &qca_soc_data_qca6390},
> { .compatible = "qcom,qca9377-bt" },
> + { .compatible = "qcom,qca9379-bt" },
Let's don't grow this that way. Use existing fallback.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-08-05 5:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 4:01 [PATCH 0/4] Add support for QCA9379 hw1.0 SDIO WiFi/BT Felix Kaechele
2024-08-05 4:01 ` [PATCH 1/4] mmc: sdio: add Qualcomm QCA9379-3 SDIO id Felix Kaechele
2024-08-05 10:04 ` Ulf Hansson
2024-08-05 4:01 ` [PATCH 2/4] wifi: ath10k: add support for QCA9379 hw1.0 SDIO Felix Kaechele
2024-08-05 4:01 ` [PATCH 3/4] dt-bindings: net: bluetooth: qualcomm: add QCA9379 compatible Felix Kaechele
2024-08-05 5:31 ` Krzysztof Kozlowski
2024-08-13 22:11 ` Felix Kaechele
2024-08-14 6:14 ` Krzysztof Kozlowski
2024-08-05 4:01 ` [PATCH 4/4] Bluetooth: hci_qca: add compatible for QCA9379 Felix Kaechele
2024-08-05 5:31 ` Krzysztof Kozlowski [this message]
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=88d08de1-ce0f-4fe2-975b-29e451f5659e@kernel.org \
--to=krzk@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=felix@kaechele.ca \
--cc=jjohnson@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=quic_bgodavar@quicinc.com \
--cc=quic_rjliao@quicinc.com \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.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;
as well as URLs for NNTP newsgroup(s).