On Sun, Feb 11, 2024 at 12:32 AM Jonathan LoBue <jlobue10@xxxxxxxxx> wrote: > > From 0aed4d398be185d43b92db63693bb1c5c6a8a78b Mon Sep 17 00:00:00 2001 > From: Jonathan LoBue <jlobue10@xxxxxxxxx> > Date: Sat, 10 Feb 2024 12:28:35 -0800 > Subject: [PATCH 1/2] iio: accel: bmc150: ASUS ROG ALLY Abort Loading Something went wrong, please use `git send-email ...` to send patches. > This portion of the patch series aborts the loading of the bmc150 driver > upon DMI board match for ASUS ROG ALLY and Ayaneo Air Plus (requested by > ChimeraOS dev). ... > + if (dmi_match(DMI_BOARD_NAME, "RC71L") || (dmi_match(DMI_BOARD_NAME, "AB05-AMD") && dmi_match(DMI_PRODUCT_NAME, "AIR Plus"))) > + return -ENODEV; // Abort loading bmc150 for ASUS ROG ALLY, Ayaneo Air Plus Please, make this as the proper table (see many examples in drivers/platform/x86/ folder on how to do that). ... Speaking of the PDx86 subsystem, OTOH maybe we want the quirk patch to be outside of IIO and enumerate the IIO drivers based on i2c/spi ID tables (there are also examples unde PDx86 folder for such tricks). Hans, Ilpo, what do you think? (Jonathan, please also include Hans in the similar cases in the future with ACPI IDs and related ambiguity.) -- With Best Regards, Andy Shevchenko
