From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: liziyao@uniontech.com
Cc: "Alex Lanzano" <lanzano.alex@gmail.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"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,
"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: Mon, 11 Aug 2025 16:08:52 +0300 [thread overview]
Message-ID: <aJnrZNCpBYD92-n1@smile.fi.intel.com> (raw)
In-Reply-To: <20250730-bmi270-gpd-acpi-v1-1-1ffc85b17266@uniontech.com>
On Wed, Jul 30, 2025 at 08:56:16PM +0800, 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.
I think I saw this patch already and there was even an (unfinished)
discussion...
https://lore.kernel.org/linux-iio/20250730-bmi270-gpd-acpi-v1-1-1ffc85b17266@uniontech.com/
So, why are you sending the same patch again?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-08-11 13:08 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
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 [this message]
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=aJnrZNCpBYD92-n1@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--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®