Re: [PATCH 3/3] mmc: sdhci-acpi: exclude INT33BB:00 from ACPI binding on Lenovo N22

Next message: Breno Leitao: "[PATCH v2 3/5] workqueue: set WQ_AFFN_CACHE_SHARD as the default affinity scope"
Previous message: Breno Leitao: "[PATCH v2 2/5] workqueue: add WQ_AFFN_CACHE_SHARD affinity scope"
In reply to: Nelson Johnson: "[PATCH 3/3] mmc: sdhci-acpi: exclude INT33BB:00 from ACPI binding on Lenovo N22"
Next in thread: Adrian Hunter: "Re: [PATCH 0/3] mmc: Lenovo N22 Braswell SD slot fixes"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

From: Andy Shevchenko

Date: Fri Mar 20 2026 - 14:02:41 EST

On Mon, Mar 16, 2026 at 04:23:25PM -0500, Nelson Johnson wrote:
> On the Lenovo N22, the firmware exposes the Braswell SD controller through both PCI 0000:00:12.0 and ACPI INT33BB:00. The ACPI path for INT33BB:00 never finishes probing on this machine and repeatedly defers, which leaves the slot in the broken ACPI path instead of letting the working PCI path own the controller.
>
> Return -ENODEV early for INT33BB:00 on the Lenovo N22 so that sdhci-acpi does not bind this machine-specific firmware node. That leaves the controller to the PCI SDHCI driver, which is the path that works once the N22-specific runtime PM and card-detect quirks are applied.
>
> Scope the exclusion to the Lenovo N22 DMI match so other INT33BB systems continue to use the normal ACPI handling.

This should be done somewhere in drivers/acpi/x86/lpss.c I believe. That's the
driver that responsible for ACPI enumeration of LPSS devices on Braswell
machines.

--
With Best Regards,
Andy Shevchenko