STRUCT FSL_MC_DRIVER(9)

🌸 struct fsl_mc_driver(9) — Kernel API Manual, bestie edition 🌸

okay so this is the page for struct fsl_mc_driver from the Kernel API Manual, and honestly? she's giving structural support, she's giving the blueprint, and she is the whole personality of an MC object device driver object. let's get into it 💅

---

✨ NAME ✨

struct fsl_mc_driver — the MC object device driver object. yeah. that's her. 💖

---

🦋 SYNOPSIS 🦋

here's the shape of her, no edits, no vibes-based changes, exactly what you're working with:

struct fsl_mc_driver {
    struct device_driver driver;
    const struct fsl_mc_device_id *match_id_table;
    int (*probe)(struct fsl_mc_device *dev);
    void (*remove)(struct fsl_mc_device *dev);
    void (*shutdown)(struct fsl_mc_device *dev);
    int (*suspend)(struct fsl_mc_device *dev, pm_message_t state);
    int (*resume)(struct fsl_mc_device *dev);
    bool driver_managed_dma;
 };

like, she's a struct, she has a bool, she has function pointers — she's literally everything 🎀

---

👑 Members 👑

okay so these are her members and each one is a whole little main character:

• driver — the generic device driver. the foundational one. the base layer. the root of the whole fit ✨
• match_id_table — a table of supported device matching Ids. think of it like her list of who she'll match with — if your device's Id isn't on the list, it's not happening, and that's on periodt 💀
• probe — function called when a device is added. the "hiii, you're here!!" moment 🫶
• remove — function called when a device is removed. the goodbye callback. she's not crying, you're crying 😭
• shutdown — function called at shutdown time to quiesce the device. the calm-down-and-chill phase before everything powers off 🌙
• suspend — function called when a device is stopped. nap time, but make it kernel-level ⭐
• resume — function called when a device is resumed. she's awake!! she's back!! 🔥
• driver_managed_dma — this one's a whole essay so buckle in: it means the device driver doesn't use the kernel DMA API for DMA. for most device drivers, no need to care about this flag as long as all DMAs are handled through the kernel DMA API. for some special ones — for example VFIO drivers — they know how to manage the DMA themselves and set this flag so that the IOMMU layer will allow them to setup and manage their own I/O address space. so like, it's a "i got it, don't worry about me" flag. highkey trust issues in reverse 💜

---

🧚 Description 🧚

so what is she? struct fsl_mc_driver is the generic DPAA device driver object for device drivers that are registered with a DPRC bus. and here's the crucial part, bestie, don't miss it: this structure is to be embedded in each device-specific driver structure. like, she's not the whole outfit, she's the base layer you build the outfit on. iykyk ✨

🌈 fr fr, embed her — don't just point at her. that's the whole assignment.

---

💜 SEE ALSO 💜

go read these next, they're all connected and they all ate:

• kernel file ./include/linux/fsl/mc.h
• enum fsl_mc_pool_type(9)
• struct fsl_mc_resource(9)
• struct fsl_mc_device_irq(9)
• struct fsl_mc_obj_desc(9)
• struct fsl_mc_device(9)
• struct fsl_mc_io(9)
• struct fsl_mc_version(9)
• struct dpbp_attr(9)
• struct dpcon_attr(9)
• struct dpcon_notification_cfg(9)

---

and that's the page, bestie 🌸 kisses from the ./include/linux/fsl directory, dated October 2026, brought to you by the struct fsl_mc_driver(9) girlies. go embed a struct. slay 🎀✨💅