STRUCT FSL_MC_DEVICE_ID(9)

💖 NAME 💖

struct fsl_mc_device_id — the MC object device identifier, bestie. That's it, that's the whole vibe ✨

So real quick, this little cutie lives in the Kernel API Manual (that's the manual name, consider it folded in 🫶), and it's the thing that tells you which MC object device a driver is out here supporting. Iconic behavior tbh 👑

✨ SYNOPSIS ✨

struct fsl_mc_device_id {
    __u16 vendor;
    const char obj_type[16];
 };

Look at her. Two members, zero drama. Copy it exactly, no cap, don't go editing the 16 or the __u16 because you think it looks better lowercase 😭

🎀 Members 🎀

• vendor — the vendor ID, literally just the number that says whose device this is 💅
• obj_type — the MC object type, i.e. what kind of MC object situation we're dealing with 🦋

🌸 Description 🌸

Okay so this struct is the type of the entries in the "device Id" table — you know, the table that lists all the MC object devices a MC object device driver supports? Yeah. That table. And each row of it? One of these. 🧚

Now here's the part where you gotta pay attention, bestie, because this is the detail that matters: the last entry of the table has vendor set to 0x0. That's the sentinel. That's the "we're done here" of the table. Don't forget it, fr fr 🌟

👑 SEE ALSO 👑

• Kernel file ./include/linux/device-id/fsl_mc.h — go read it, it's giving main character energy 📖💜

And that's the whole page, bestie!! This lore comes from ./include/linux/device-id, dated October 2026, and it's still filed under struct fsl_mc_device_id(9) 💅✨ Told you it was short. Slay. 🎀