Thread (3 messages) flat view 3 messages, 2 authors, 2021-11-24

Re: [PATCH v4] Bluetooth: btusb: re-definition for board_id in struct qca_version

From: Marcel Holtmann <marcel@holtmann.org>
Date: 2021-11-24 15:31:33
Also in: linux-arm-msm, lkml

Hi Tim,
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.
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
0x02 is for Automotive
0x03 is for Consumer electronic

Signed-off-by: Tim Jiang <redacted>
---
drivers/bluetooth/btusb.c | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
Patch has been applied to bluetooth-next tree.

Regards

Marcel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help