[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <1593EED1-5745-49D1-B17A-F4C553F28644@holtmann.org>
Date: Mon, 15 Nov 2021 18:30:27 +0100
From: Marcel Holtmann <marcel@...tmann.org>
To: tjiang@...eaurora.org
Cc: Johan Hedberg <johan.hedberg@...il.com>,
Luiz Augusto von Dentz <luiz.dentz@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-bluetooth <linux-bluetooth@...r.kernel.org>,
MSM <linux-arm-msm@...r.kernel.org>,
Balakrishna Godavarthi <bgodavar@...eaurora.org>,
c-hbandi@...eaurora.org, Hemantg <hemantg@...eaurora.org>,
Matthias Kaehlcke <mka@...omium.org>,
Rocky Liao <rjliao@...eaurora.org>, zijuhu@...eaurora.org
Subject: Re: [PATCH v3] Bluetooth: btusb: re-definition for board_id in struct
qca_version
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
Powered by blists - more mailing lists