Re: [PATCH 2/4] iio: imu: bmi270: Match PNP ID found on OneXPlayer X1 Pro (AMD)

Jonathan Cameron <[email protected]> Sun, 2 Aug 2026 18:58:14 +0100
Newsgroups org.kernel.vger.linux-iio,org.kernel.vger.linux-kernel
Message-ID <20260802185814.431a6425@jic23-huawei>
On Fri, 31 Jul 2026 21:53:23 +0200
Philip Mueller <[email protected]> wrote:

> The OneXPlayer X1 Pro (AMD) uses 10EC5280 rather than BMI0260 or BOSC0260 as PNP ID.

Groan.  That's a realtech PCI ID not a PNP or ACPI ID.  Those can be used in
ACPI but far as I know realtech never made IMUs.  

More of an issue is this ID is already in the bmi160_i2c driver.
If they are using it for both parts we have a nasty problem
and it is probably a thing to fix as a platform quirk rather than in the
drivers.

There is a bunch of history of this ID 
https://lore.kernel.org/linux-iio/?q=10EC5280

IIRC Bosch provide their own mega driver supporting all parts from one module
and then do part detection.  Thus wrong tables often work :(

Jonathan



> Adding the ID will enable the BMI260 accelerometer on the device using the bmi270 driver.
> 
> Closes: https://github.com/ublue-os/bazzite/issues/4805
> Cc: [email protected] # 6.18+
> Signed-off-by: Philip Mueller <[email protected]>
> ---
>  drivers/iio/imu/bmi270/bmi270_i2c.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/iio/imu/bmi270/bmi270_i2c.c b/drivers/iio/imu/bmi270/bmi270_i2c.c
> index 036c6f0f7cd4..d7faebcbd2fa 100644
> --- a/drivers/iio/imu/bmi270/bmi270_i2c.c
> +++ b/drivers/iio/imu/bmi270/bmi270_i2c.c
> @@ -45,6 +45,8 @@ static const struct acpi_device_id bmi270_acpi_match[] = {
>  	{ "BMI0260",  (kernel_ulong_t)&bmi260_chip_info },
>  	/* OrangePi Neo 2026 (since BIOS BCPH01_V1.20), etc. */
>  	{ "BOSC0260", (kernel_ulong_t)&bmi260_chip_info },
> +	/* OneXPlayer X1 Pro (AMD), etc. */
> +	{ "10EC5280", (kernel_ulong_t)&bmi260_chip_info },
>  	{ }
>  };
>  MODULE_DEVICE_TABLE(acpi, bmi270_acpi_match);