From: David Lechner <dlechner@baylibre.com>
To: liziyao@uniontech.com, "Alex Lanzano" <lanzano.alex@gmail.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Yao Zi <ziyao@disroot.org>, WangYuli <wangyuli@uniontech.com>,
Jun Zhan <zhanjun@uniontech.com>
Subject: Re: [PATCH] iio: imu: bmi270: Match ACPI ID found on newer GPD firmware
Date: Wed, 30 Jul 2025 12:46:55 -0500 [thread overview]
Message-ID: <cf90537d-bdb3-4770-91f1-4039c727f7c6@baylibre.com> (raw)
In-Reply-To: <20250730-bmi270-gpd-acpi-v1-1-1ffc85b17266@uniontech.com>
On 7/30/25 7:56 AM, Cryolitia PukNgae via B4 Relay wrote:
> From: Cryolitia PukNgae <liziyao@uniontech.com>
>
> Some GPD devices ship a buggy firmware that describes on-device BMI260
> with ACPI ID "BMI0160". Since this is fixed in BIOS update v0.40,
> let's match the correct ID to detect the device. The buggy ID "BMI0160"
> is kept as well to maintain compatibility with older firmwares.
>
> Signed-off-by: Cryolitia PukNgae <liziyao@uniontech.com>
> ---
> Some GPD devices ship a buggy firmware that describes on-device BMI260
> with ACPI ID "BMI0160". Since this is fixed in BIOS update v0.40[1],
> let's match the correct ID to detect the device. The buggy ID "BMI0160"
> is kept as well to maintain compatibility with older firmwares.
>
> Link: http://download.softwincn.com/WIN%20Max%202024/Max2-7840-BIOS-V0.41.zip
>
> [1]. See the update nodes in the archive file above
> ---
> 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 c77839b03a969f6f149c025a0305c4b9b8ac6571..b909a421ad0176ee414f2f96ff09db2297586ded 100644
> --- a/drivers/iio/imu/bmi270/bmi270_i2c.c
> +++ b/drivers/iio/imu/bmi270/bmi270_i2c.c
> @@ -41,6 +41,8 @@ static const struct i2c_device_id 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 },
> + /* GPD Win Max 2 2023(sincice BIOS v0.40), etc. */
Is this supposed to say "since" instead of "sincice"?
> + { "BMI0260", (kernel_ulong_t)&bmi260_chip_info },
> { }
> };
>
>
> ---
> base-commit: 0db240bc077fd16cc16bcecfd7f4645bc474aa7e
> change-id: 20250206-bmi270-gpd-acpi-de4d12bce567
>
> Best regards,
next prev parent reply other threads:[~2025-07-30 17:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 12:56 Cryolitia PukNgae via B4 Relay
2025-07-30 17:46 ` David Lechner [this message]
2025-07-30 20:57 ` Andy Shevchenko
2025-07-30 21:11 ` Andy Shevchenko
2025-07-31 3:05 ` Cryolitia PukNgae
2025-07-31 9:46 ` Andy Shevchenko
2025-08-11 13:08 ` Andy Shevchenko
2025-08-11 13:10 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2025-02-06 7:09 Cryolitia PukNgae via B4 Relay
2025-02-07 17:12 ` Alex Lanzano
2025-02-08 13:30 ` Jonathan Cameron
2025-07-30 10:16 ` Cryolitia PukNgae
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=cf90537d-bdb3-4770-91f1-4039c727f7c6@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=jic23@kernel.org \
--cc=lanzano.alex@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liziyao@uniontech.com \
--cc=nuno.sa@analog.com \
--cc=wangyuli@uniontech.com \
--cc=zhanjun@uniontech.com \
--cc=ziyao@disroot.org \
/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
all inboxes | Powered by JetHome®