STRUCT LPC_DRIVER_DATA(9)

💅 struct lpc_driver_data(9) — from the Kernel API Manual, bestie

okay so welcome to the glow-up of struct lpc_driver_data(9), a page straight out of the Kernel API Manual. she's small, she's specific, and she's carrying the whole hardware-quirk situation on her back. let's get into it ✨

---

🌸 NAME 🌸

struct lpc_driver_data — the driver data that gets attached to a DMI device ID so the kernel can flag hardware quirks. it's giving "notes app but for silicon" 💅

---

🦋 SYNOPSIS 🦋

struct lpc_driver_data {
    u32 quirks;
    u16 quirk_mmio_memory_base;
    const char *quirk_acpi_id;
    const char *quirk_aml_mutex_name;
 };

look at her. four fields. no notes. 👑

---

✨ Members ✨

• quirks — a bitfield, bestie, and it's composed of quirks from CROS_EC_LPC_QUIRK_*. think of it as a little mood board of everything weird your hardware does 🎀
• quirk_mmio_memory_base — the first I/O port addressing EC mapped memory. it's only in the picture when the quirk ...REMAP_MEMORY is set, so don't come for her if she's chilling at zero otherwise 🙈
• quirk_acpi_id — an ACPI HID, and its whole job is being used to find the ACPI device. lowkey a little detective 🔍
• quirk_aml_mutex_name — the name of an AML mutex, and yes it's used to protect access to the Microchip EC. she's the bodyguard of the group chat 🫶

---

💜 SEE ALSO 💜

• the kernel file ./drivers/platform/chrome/cros_ec_lpc.c
• struct cros_ec_lpc(9) — her bestie, obviously, go read that one next 📖

---

ngl this struct is tiny but she's doing so much work. respect the quirk fields, they're carrying the compatibility of an entire EC fr fr 🔥

---

and that's the page!! slay 💖 this one lives under ./drivers/platform/chrome, dated October 2026, and it's filed as struct lpc_driver_data(9). mwah, go touch some hardware (carefully) ⭐🌈🍓