From: Jonathan Cameron <jic23@kernel.org>
To: Philip Mueller <philm@manjaro.org>
Cc: "Thierry Reding" <thierry.reding@gmail.com>,
"Alex Lanzano" <lanzano.alex@gmail.com>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] iio: imu: bmi270: Match PNP ID found on OrangePi Neo 2026
Date: Sun, 2 Aug 2026 18:47:23 +0100 [thread overview]
Message-ID: <20260802184723.22554361@jic23-huawei> (raw)
In-Reply-To: <20260731195325.44453-2-philm@manjaro.org>
On Fri, 31 Jul 2026 21:53:22 +0200
Philip Mueller <philm@manjaro.org> wrote:
> OrangePi Neo devices use BMI260 sensors in their hardware.
> In older firmware they used "BMI0260" as their ID. In newer firmware
> however they switched to "BOSC0260" as their ID for the sensors.
> This change is also seen DSDT tables within newer device firmware.
>
> Adding the PNP ID to bmi270 driver will load the driver properly on the device.
Hi Philip
The new one is not a PNP ID. Those only have 3 letters.
They have switched over to using an ACPI ID - which is the other thing you
are allowed to put in _HID in ACPI.
Good to see they are using a valid format at least and hopefully Bosch
have indeed allocated that code to this device. So rare case of a correct
update.
FWIW BMI was the PNP ID of the Benson medical instruments company.
So with a minor commit text update to reflect that I'll be happy to pick
this one up.
Thanks
Jonathan
>
> Cc: stable@vger.kernel.org # 6.18+
> Signed-off-by: Philip Mueller <philm@manjaro.org>
> ---
> 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 7c035e82e6e9..036c6f0f7cd4 100644
> --- a/drivers/iio/imu/bmi270/bmi270_i2c.c
> +++ b/drivers/iio/imu/bmi270/bmi270_i2c.c
> @@ -43,6 +43,8 @@ static const struct acpi_device_id bmi270_acpi_match[] = {
> { "BMI0160", (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. */
> + { "BOSC0260", (kernel_ulong_t)&bmi260_chip_info },
> { }
> };
> MODULE_DEVICE_TABLE(acpi, bmi270_acpi_match);
next prev parent reply other threads:[~2026-08-02 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 19:53 [PATCH 0/4] iio: imu: bmi270: Match PNP ID found on gaming handheld firmwares Philip Mueller
2026-07-31 19:53 ` [PATCH 1/4] iio: imu: bmi270: Match PNP ID found on OrangePi Neo 2026 Philip Mueller
2026-08-02 17:47 ` Jonathan Cameron [this message]
2026-07-31 19:53 ` [PATCH 2/4] iio: imu: bmi270: Match PNP ID found on OneXPlayer X1 Pro (AMD) Philip Mueller
2026-08-02 17:58 ` Jonathan Cameron
2026-08-10 19:04 ` Andy Shevchenko
2026-07-31 19:53 ` [PATCH 3/4] iio: imu: bmi270: add BOSC0160 PNP ID for gaming handhelds Philip Mueller
2026-08-02 18:01 ` Jonathan Cameron
2026-08-10 19:05 ` Andy Shevchenko
2026-07-31 19:53 ` [PATCH 4/4] iio: imu: bmi270: fix typo found in dc757dc Philip Mueller
2026-08-02 18:02 ` Jonathan Cameron
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=20260802184723.22554361@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=lanzano.alex@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=philm@manjaro.org \
--cc=thierry.reding@gmail.com \
/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