Re: [PATCH 3/4] iio: imu: bmi270: add BOSC0160 PNP ID for gaming handhelds
Jonathan Cameron <[email protected]> Sun, 2 Aug 2026 19:01:21 +0100
| Newsgroups | org.kernel.vger.linux-iio,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <20260802190121.73d3f1ed@jic23-huawei> |
On Fri, 31 Jul 2026 21:53:24 +0200 Philip Mueller <[email protected]> wrote: > Adding BOSC0160 as PNP ID will enable more gaming > handhelds using a BMI260 sensor with this PNP ID > to properly use the bmi270 driver. Very short wrap. Go up to 75 characters. As in early one, ACPI ID not PNP ID. Ideally we'd also have confirmation from bosch that they have assigned the IDs like this. I ask in particular because they have multiple parts with 160 numbers and they aren't all supported by this driver. E.g. bmg160 which is a gyro only part. + Can we have at least one example part that is using this ID as a comment inline. Some of those earlier discussions of bosch IDs identified ones that we were fairly sure were only ever used in prototype devices. Jonathan > > Cc: [email protected] # 6.18+ > Signed-off-by: Philip Mueller <[email protected]> > --- > drivers/iio/imu/bmi270/bmi270_i2c.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/iio/imu/bmi270/bmi270_i2c.c b/drivers/iio/imu/bmi270/bmi270_i2c.c > index d7faebcbd2fa..839e71b65f05 100644 > --- a/drivers/iio/imu/bmi270/bmi270_i2c.c > +++ b/drivers/iio/imu/bmi270/bmi270_i2c.c > @@ -41,6 +41,7 @@ MODULE_DEVICE_TABLE(i2c, bmi270_i2c_id); > static const struct acpi_device_id bmi270_acpi_match[] = { > /* GPD Win Mini, Aya Neo AIR Pro, OXP Mini Pro, etc. */ > { "BMI0160", (kernel_ulong_t)&bmi260_chip_info }, > + { "BOSC0160", (kernel_ulong_t)&bmi260_chip_info }, > /* GPD Win Max 2 2023(sincice BIOS v0.40), etc. */ > { "BMI0260", (kernel_ulong_t)&bmi260_chip_info }, > /* OrangePi Neo 2026 (since BIOS BCPH01_V1.20), etc. */