From: Jonathan Cameron <jic23@kernel.org>
To: Jonathan LoBue <jlobue10@gmail.com>
Cc: linux-iio@vger.kernel.org, andy.shevchenko@gmail.com,
hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com,
jagathjog1996@gmail.com, luke@ljones.dev,
benato.denis96@gmail.com, lkml@antheas.dev,
derekjohn.clark@gmail.com
Subject: Re: [PATCH v5 1/2] iio: accel: bmc150: Duplicate ACPI entries
Date: Fri, 16 Feb 2024 11:37:06 +0000 [thread overview]
Message-ID: <20240216113706.695b22fc@jic23-huawei> (raw)
In-Reply-To: <20240215182425.57334-1-jlobue10@gmail.com>
On Thu, 15 Feb 2024 10:24:25 -0800
Jonathan LoBue <jlobue10@gmail.com> wrote:
> This patch adds a description of the duplicate ACPI identifier issue
> between devices using bmc150 and bmi323.
Title of patch doesn't reflect what is going on.
If there are no other changes needed I can tweak that whilst applying
to
iio: accel: bmc150: Document duplicate ACPI entries with bmi323 driver
>
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> Co-developed-by: Luke D. Jones <luke@ljones.dev>
> Signed-off-by: Luke D. Jones <luke@ljones.dev>
> Co-developed-by: Denis Benato <benato.denis96@gmail.com>
> Signed-off-by: Denis Benato <benato.denis96@gmail.com>
> Co-developed-by: Antheas Kapenekakis <lkml@antheas.dev>
> Signed-off-by: Antheas Kapenekakis <lkml@antheas.dev>
> Signed-off-by: Jonathan LoBue <jlobue10@gmail.com>
> ---
> drivers/iio/accel/bmc150-accel-i2c.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/drivers/iio/accel/bmc150-accel-i2c.c b/drivers/iio/accel/bmc150-accel-i2c.c
> index ee1ba134ad42..353271e23235 100644
> --- a/drivers/iio/accel/bmc150-accel-i2c.c
> +++ b/drivers/iio/accel/bmc150-accel-i2c.c
> @@ -224,6 +224,19 @@ static const struct acpi_device_id bmc150_accel_acpi_match[] = {
> {"BMA250E"},
> {"BMC150A"},
> {"BMI055A"},
> + /*
> + * The "BOSC0200" identifier used here is not unique to devices using
> + * bmc150. The same "BOSC0200" identifier is found in the ACPI tables of
> + * the ASUS ROG ALLY and Ayaneo AIR Plus which both use a Bosch BMI323
> + * chip. This creates a conflict with duplicate ACPI identifiers which
> + * multiple drivers want to use. Fortunately, when the bmc150 driver
> + * starts to load on the ASUS ROG ALLY, the chip ID check portion fails
> + * (correctly) because the chip IDs received (via i2c) are unique between
> + * bmc150 and bmi323 and a dmesg output similar to this:
> + * "bmc150_accel_i2c i2c-BOSC0200:00: Invalid chip 0" can be seen.
> + * This allows the bmi323 driver to take over for ASUS ROG ALLY, and
> + * other devices using the bmi323 chip.
> + */
> {"BOSC0200"},
> {"BSBA0150"},
> {"DUAL250E"},
next prev parent reply other threads:[~2024-02-16 11:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 18:19 [PATCH v5 0/2] Add bmi323 support for ASUS ROG ALLY J Lo
2024-02-15 18:24 ` [PATCH v5 1/2] iio: accel: bmc150: Duplicate ACPI entries Jonathan LoBue
2024-02-16 11:37 ` Jonathan Cameron [this message]
2024-02-16 14:30 ` Jonathan LoBue
2024-02-16 15:49 ` Jonathan Cameron
2024-02-15 18:24 ` [PATCH v5 2/2] iio: imu: bmi323: Add and enable ACPI Match Table Jonathan LoBue
2024-02-16 11:41 ` Jonathan Cameron
2024-02-16 11:35 ` [PATCH v5 0/2] Add bmi323 support for ASUS ROG ALLY Jonathan Cameron
2024-02-16 12:01 ` Hans de Goede
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=20240216113706.695b22fc@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=benato.denis96@gmail.com \
--cc=derekjohn.clark@gmail.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jagathjog1996@gmail.com \
--cc=jlobue10@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=luke@ljones.dev \
/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