From: Marcel Holtmann <marcel@holtmann.org>
To: tjiang@codeaurora.org
Cc: Johan Hedberg <johan.hedberg@gmail.com>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
MSM <linux-arm-msm@vger.kernel.org>,
Balakrishna Godavarthi <bgodavar@codeaurora.org>,
c-hbandi@codeaurora.org, Hemantg <hemantg@codeaurora.org>,
Matthias Kaehlcke <mka@chromium.org>,
Rocky Liao <rjliao@codeaurora.org>,
zijuhu@codeaurora.org
Subject: Re: [PATCH v3] Bluetooth: btusb: re-definition for board_id in struct qca_version
Date: Mon, 15 Nov 2021 18:30:27 +0100 [thread overview]
Message-ID: <1593EED1-5745-49D1-B17A-F4C553F28644@holtmann.org> (raw)
In-Reply-To: <96d03a2b0bd50da90a20990c42a814d9@codeaurora.org>
Hi Tim,
> the following is the explanation from qc btsoc team:
>
> The board ID should be split into two bytes.
> The 1st byte is chip ID, and the 2nd byte is platform ID.
> For example, board ID 0x010A, 0x01 is platform ID. 0x0A is chip ID.
> Currently we have several platforms, and platform IDs are continuously added.
> We would not distinguish different chips if we get these mixed up.
> Platform ID:
> • 0x00 is for Mobile
> • 0x01 is for X86( ID # from 257)
> • 0x02 is for Automotive(ID# from 513 )
> • 0x03 is for Consumer electronic( ID# from 769)
> …
then use u8 chip_id and u8 platform_id in the data structure and add description like above when you combine chip_id and platform_id into board_id.
Regards
Marcel
prev parent reply other threads:[~2021-11-15 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 7:01 [PATCH v3] Bluetooth: btusb: re-definition for board_id in struct qca_version tjiang
2021-11-09 9:37 ` Marcel Holtmann
2021-11-15 10:04 ` tjiang
2021-11-15 17:30 ` Marcel Holtmann [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=1593EED1-5745-49D1-B17A-F4C553F28644@holtmann.org \
--to=marcel@holtmann.org \
--cc=bgodavar@codeaurora.org \
--cc=c-hbandi@codeaurora.org \
--cc=hemantg@codeaurora.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=mka@chromium.org \
--cc=rjliao@codeaurora.org \
--cc=tjiang@codeaurora.org \
--cc=zijuhu@codeaurora.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).