Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan LoBue <jlobue10@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Jonathan Cameron <jic23@kernel.org>
Cc: "Hans De Goede" <hdegoede@redhat.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	jagathjog1996@gmail.com, luke@ljones.dev,
	benato.denis96@gmail.com, linux-iio@vger.kernel.org,
	lkml@antheas.dev, derekjohn.clark@gmail.com
Subject: Re: [PATCH 1/2] iio: accel: bmc150: ASUS ROG ALLY Abort Loading
Date: Mon, 12 Feb 2024 18:47:27 -0800	[thread overview]
Message-ID: <5794873.DvuYhMxLoT@nobara-ally-pc> (raw)
In-Reply-To: <CAHp75VfJeMZUBO0c9gr=ymee8jqu0xJQRwrg798Trrmr6ox5gw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]

On Monday, February 12, 2024 1:46:21 AM PST Andy Shevchenko wrote:
> Even if fixed (which has to be done anyway) it can be undone in old
> firmwares — there is no solution to make all affected users update
> firmware. Do we have real products on the market with the wrong ID (I
> assume we do)?

After some conversations with other devs today, we retested and confirmed
that the DMI quirks to abort loading of bmc150 is actually unnecessary.
There was some confusion among us about why they had tried that approach
in the past. The bmc150 driver does in fact start to load on ASUS ROG ALLY
with a "BOSC0200" ACPI match, but when it gets to the chip id check portion
it correctly aborts loading the driver for mismatched chip ID. This allows
the bmi323 driver to pick it up properly with the "BOSC0200" ACPI match
table match. Tested and confirmed working on my end with the submitted
v1 patch. The DMI quirks and any modifications to bmc150 driver has been
dropped. Thanks all for the feedback and help.

Best Regards,
Jon LoBue



[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2024-02-13  2:47 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                         ` [PATCH v2 2/2] iio: imu: bmi323: Add and enable ACPI Match Table Jonathan LoBue
2024-02-14  9:39                           ` 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                 ` Jonathan LoBue [this message]
2024-02-10 22:34         ` [PATCH " 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=5794873.DvuYhMxLoT@nobara-ally-pc \
    --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