From: Johan Hovold <johan@kernel.org>
To: Tim Jiang <quic_tjiang@quicinc.com>
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 1/2] Bluetooth: hci_qca: adjust qca btsoc type print expression
Date: Thu, 27 Jul 2023 09:50:39 +0200 [thread overview]
Message-ID: <ZMIhz_ULbfwxZjZ8@hovoldconsulting.com> (raw)
In-Reply-To: <11643479-3411-381e-4708-7259f6a15668@quicinc.com>
On Thu, Jul 27, 2023 at 03:34:53PM +0800, Tim Jiang wrote:
> On 7/27/23 15:27, Johan Hovold wrote:
> > On Thu, Jul 27, 2023 at 12:40:10PM +0800, Tim Jiang wrote:
> >> @@ -1762,10 +1763,32 @@ static int qca_setup(struct hci_uart *hu)
> >> */
> >> set_bit(HCI_QUIRK_SIMULTANEOUS_DISCOVERY, &hdev->quirks);
> >>
> >> - bt_dev_info(hdev, "setting up %s",
> >> - qca_is_wcn399x(soc_type) ? "wcn399x" :
> >> - (soc_type == QCA_WCN6750) ? "wcn6750" :
> >> - (soc_type == QCA_WCN6855) ? "wcn6855" : "ROME/QCA6390");
> >> + switch (soc_type) {
> >> + case QCA_AR3002:
> >> + soc_name = "ar300x";
> >> + break;
> >> + case QCA_ROME:
> >> + soc_name = "ROME";
> >> + break;
> >> + case QCA_QCA6390:
> >> + soc_name = "QCA6390";
> >> + break;
> >> + case QCA_WCN3990:
> >> + case QCA_WCN3991:
> >> + case QCA_WCN3998:
> >> + soc_name = "wcn399x";
> >> + break;
> >> + case QCA_WCN6750:
> >> + soc_name = "wcn6750";
> >> + break;
> >> + case QCA_WCN6855:
> >> + soc_name = "wcn6855";
> >> + break;
> > I still think the above should be sorted (alphabetically) as maintaining
> > these lists otherwise soon becomes harder than it should be. And similar
> > throughout the driver.
> [Tim] Hi Johan: I think we no need to sort it, we only add the new btsoc
> name following the older one, for example , ar300x is the oldest , ROME
> is new than ar300x, actually qca2066 is newer version chip than qca6390,
> so I does not think we need to sort it.
Possibly, but generally this becomes hard to maintain and eventually
someone will need to sort these entries anyway. Therefore it's generally
a good idea to just do so from the start.
But it was good that you replied so that we know that this comment was
not just missed or ignored.
> >> + default:
> >> + soc_name = "unknown soc";
> >> + break;
> >> + }
> >> + bt_dev_info(hdev, "setting up %s", soc_name);
Johan
next prev parent reply other threads:[~2023-07-27 7:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 4:40 [PATCH v13 0/2] Bluetooth: hci_qca: Add support for Qualcomm Bluetooth SoC QCA2066 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 [this message]
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
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=ZMIhz_ULbfwxZjZ8@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=johan.hedberg@gmail.com \
--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 \
--cc=quic_tjiang@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