From: Tim Jiang <quic_tjiang@quicinc.com>
To: Johan Hovold <johan@kernel.org>
Cc: <marcel@holtmann.org>, <luiz.dentz@gmail.com>,
<johan.hedberg@gmail.com>, <linux-kernel@vger.kernel.org>,
<linux-bluetooth@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <quic_bgodavar@quicinc.com>,
<quic_hemantg@quicinc.com>
Subject: Re: [PATCH v13 2/2] Bluetooth: hci_qca: Add support for Qualcomm Bluetooth SoC QCA2066
Date: Thu, 27 Jul 2023 16:00:44 +0800 [thread overview]
Message-ID: <23d58498-60a5-9de5-0bf1-71bf636da110@quicinc.com> (raw)
In-Reply-To: <ZMIdE1ffQEmFMC8V@hovoldconsulting.com>
On 7/27/23 15:30, Johan Hovold wrote:
> On Thu, Jul 27, 2023 at 12:40:11PM +0800, Tim Jiang wrote:
>> This patch adds support for QCA2066 firmware patch and NVM downloading.
>> as the RF performance of QCA2066 SOC chip from different foundries may
>> vary. Therefore we use different NVM to configure them based on board ID.
>>
>> Signed-off-by: Tim Jiang <quic_tjiang@quicinc.com>
>> ---
>
>> @@ -1931,6 +1934,12 @@ static const struct qca_device_data qca_soc_data_wcn3998 __maybe_unused = {
>> .num_vregs = 4,
>> };
>>
>> +static const struct qca_device_data qca_soc_data_qca2066 __maybe_unused = {
>> + .soc_type = QCA_QCA2066,
>> + .num_vregs = 0,
>> +};
>> +
>> +
> Stray newline.
[Tim] sorry for this typo, will address it in v14 , thank you.
>
>> static const struct qca_device_data qca_soc_data_qca6390 __maybe_unused = {
>> .soc_type = QCA_QCA6390,
>> .num_vregs = 0,
> Johan
next prev parent reply other threads:[~2023-07-27 8:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 4:40 [PATCH v13 0/2] " Tim Jiang
2023-07-27 4:40 ` [PATCH v13 1/2] Bluetooth: hci_qca: adjust qca btsoc type print expression Tim Jiang
2023-07-27 7:27 ` Johan Hovold
2023-07-27 7:34 ` Tim Jiang
2023-07-27 7:50 ` Johan Hovold
2023-07-27 4:40 ` [PATCH v13 2/2] Bluetooth: hci_qca: Add support for Qualcomm Bluetooth SoC QCA2066 Tim Jiang
2023-07-27 7:30 ` Johan Hovold
2023-07-27 8:00 ` Tim Jiang [this message]
2023-07-27 7:25 ` [PATCH v13 0/2] " Johan Hovold
2023-07-27 7:54 ` Tim 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=23d58498-60a5-9de5-0bf1-71bf636da110@quicinc.com \
--to=quic_tjiang@quicinc.com \
--cc=johan.hedberg@gmail.com \
--cc=johan@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_hemantg@quicinc.com \
/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
all inboxes | Powered by JetHome®