From: Jonathan LoBue <jlobue10@gmail.com>
To: andy.shevchenko@gmail.com
Cc: hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com,
jic23@kernel.org, jagathjog1996@gmail.com, luke@ljones.dev,
benato.denis96@gmail.com, linux-iio@vger.kernel.org,
lkml@antheas.dev, derekjohn.clark@gmail.com,
Jonathan LoBue <jlobue10@gmail.com>
Subject: [PATCH v2 2/2] iio: imu: bmi323: Add and enable ACPI Match Table
Date: Tue, 13 Feb 2024 14:39:10 -0800 [thread overview]
Message-ID: <20240213223910.27127-1-jlobue10@gmail.com> (raw)
In-Reply-To: <CAHp75VfcHnswdXnqdtOkX31LbULu8Pa0WjM5EC96OuOBrZGTxA@mail.gmail.com>
This patch adds the ACPI match table for ASUS ROG ALLY to load the bmi323
driver with an ACPI match of "BOSC0200".
Co-developed-by: Jonathan LoBue <jlobue10@gmail.com>
Signed-off-by: Jonathan LoBue <jlobue10@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>
---
Formatting fixes, removed duplicate header, and removed ACPI_PTR
from previous submission.
Added an explanation of the duplicate ACPI identifier issue between
devices using bmc150 and bmi323.
drivers/iio/imu/bmi323/bmi323_i2c.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/drivers/iio/imu/bmi323/bmi323_i2c.c b/drivers/iio/imu/bmi323/bmi323_i2c.c
index 20a8001b9956..22826a2efc6f 100644
--- a/drivers/iio/imu/bmi323/bmi323_i2c.c
+++ b/drivers/iio/imu/bmi323/bmi323_i2c.c
@@ -93,6 +93,25 @@ static int bmi323_i2c_probe(struct i2c_client *i2c)
return bmi323_core_probe(dev);
}
+/*
+ * The "BOSC0200" ACPI identifier used here in the bmi323 driver is not
+ * unique to bmi323 devices. The same "BOSC0200" identifier is found in
+ * devices using the bmc150 chip. This creates a conflict with duplicate
+ * ACPI identifiers which multiple drivers want to use. If a non-bmi323
+ * device starts to load with this "BOSC0200" ACPI match here, then the
+ * chip id check portion should fail and the driver should relinquish the
+ * device. If and when a different driver (such as bmc150) starts to load
+ * with the "BOSC0200" ACPI match, a short reset should ensure that the
+ * device is not in a bad state during that driver initialization. This
+ * device reset does occur in both the bmi323 and bmc150 init sequences.
+ */
+
+static const struct acpi_device_id bmi323_acpi_match[] = {
+ { "BOSC0200" },
+ { }
+};
+MODULE_DEVICE_TABLE(acpi, bmi323_acpi_match);
+
static const struct i2c_device_id bmi323_i2c_ids[] = {
{ "bmi323" },
{ }
@@ -109,6 +128,7 @@ static struct i2c_driver bmi323_i2c_driver = {
.driver = {
.name = "bmi323",
.of_match_table = bmi323_of_i2c_match,
+ .acpi_match_table = bmi323_acpi_match,
},
.probe = bmi323_i2c_probe,
.id_table = bmi323_i2c_ids,
--
2.43.0
next prev parent reply other threads:[~2024-02-13 22:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 16:05 [PATCH] iio: imu: bmi323: Support loading of bmi323 driver for ASUS ROG ALLY Jonathan LoBue
2024-02-10 15:25 ` Jonathan Cameron
2024-02-10 16:23 ` Jonathan LoBue
2024-02-10 16:49 ` Jonathan Cameron
2024-02-10 20:43 ` Jonathan LoBue
2024-02-10 22:32 ` [PATCH 1/2] iio: accel: bmc150: ASUS ROG ALLY Abort Loading Jonathan LoBue
2024-02-11 17:04 ` Andy Shevchenko
2024-02-12 7:21 ` Jonathan LoBue
2024-02-12 9:46 ` Andy Shevchenko
2024-02-13 2:39 ` [PATCH v1] iio: imu: bmi323: Add and enable ACPI Match Table Jonathan LoBue
2024-02-13 10:49 ` Andy Shevchenko
2024-02-13 17:14 ` Jonathan LoBue
2024-02-13 17:29 ` Andy Shevchenko
2024-02-13 22:38 ` [PATCH v2 1/2] iio: accel: bmc150: Duplicate ACPI entries Jonathan LoBue
2024-02-14 9:35 ` Andy Shevchenko
2024-02-14 15:07 ` Jonathan LoBue
2024-02-14 15:39 ` Andy Shevchenko
2024-02-14 16:16 ` Jonathan Cameron
2024-02-13 22:39 ` Jonathan LoBue [this message]
2024-02-14 9:39 ` [PATCH v2 2/2] iio: imu: bmi323: Add and enable ACPI Match Table Andy Shevchenko
2024-02-14 15:15 ` Jonathan LoBue
2024-02-14 15:31 ` Andy Shevchenko
2024-02-14 17:35 ` Jonathan LoBue
2024-02-14 18:21 ` Andy Shevchenko
2024-02-14 16:19 ` Jonathan Cameron
2024-02-13 2:47 ` [PATCH 1/2] iio: accel: bmc150: ASUS ROG ALLY Abort Loading Jonathan LoBue
2024-02-10 22:34 ` [PATCH 2/2] iio: imu: bmi323: Add and enable ACPI Match Table Jonathan LoBue
2024-02-11 16:31 ` Jonathan Cameron
2024-02-11 17:08 ` Andy Shevchenko
2024-02-12 7:30 ` Jonathan LoBue
2024-02-12 9:50 ` Andy Shevchenko
2024-02-12 17:33 ` Jonathan LoBue
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=20240213223910.27127-1-jlobue10@gmail.com \
--to=jlobue10@gmail.com \
--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=jic23@kernel.org \
--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