STRUCT MLXREG_HOTPLUG_DEVICE(9)

💅 struct mlxreg_hotplug_device(9) 💅

okay so this is a page from the Kernel API Manual, and bestie, we're about to get so cozy with one struct. it's struct mlxreg_hotplug_device, and it's literally the whole personality of an I2C hotplug device. let's go 🫶

---

✨ NAME ✨

struct mlxreg_hotplug_device — I2C device data: (yes the colon is part of the vibe, we keep it 💅)

---

🦋 SYNOPSIS 🦋

struct mlxreg_hotplug_device {
    struct i2c_adapter *adapter;
    struct i2c_client *client;
    struct i2c_board_info *brdinfo;
    int nr;
    struct platform_device *pdev;
    enum mlxreg_hotplug_device_action action;
    void *handle;
    int (*user_handler)(void *handle, enum mlxreg_hotplug_kind kind, u8
action);
    struct mlxreg_core_hotplug_notifier *notifier;
 };

no cap, that function pointer line is long and it knows it 😭 but we don't touch it, we respect it.

---

🎀 Members 🎀

• adapter — the I2C device adapter. the adapter. the one. 💖
• client — the I2C device client. its bestie fr fr.
• brdinfo — device board information. the lore, basically.
• nr — the I2C device adapter number, like, the specific adapter this device is to be attached to. lowkey important 👑
• pdev — the platform device, but only if the device is instantiated as a platform device. conditional king ✨
• action — the action to be performed upon event receiving. what we do when the event pulls up 🙈
• handle — a user handle to be passed by the user handler function. passing notes in class, but make it kernel 💌
• user_handler — the user handler function associated with the event. the main character callback, honestly 🌟
• notifier — pointer to the event notifier block. it notifies. it's giving reliable friend energy 🦋

---

🌸 Description 🌸

okay so this struct is doing double duty and we stan a multitasking icon. it represents I2C hotplug device static data (that's the board topology, the fixed stuff, the foundation 💅) and dynamic data (that's the related kernel objects handles, the stuff that comes and goes, the drama 🌈).

so basically: the blueprint and the live handle situation, living in one struct. iconic behavior, no notes.

---

🔥 SEE ALSO 🔥

• Kernel file ./include/linux/platform_data/mlxreg.h
• enum mlxreg_wdt_type(9)
• enum mlxreg_hotplug_kind(9)
• enum mlxreg_hotplug_device_action(9)
• struct mlxreg_core_hotplug_notifier(9)
• struct mlxreg_core_data(9)
• struct mlxreg_core_item(9)
• struct mlxreg_core_platform_data(9)
• struct mlxreg_core_hotplug_platform_data(9)

like, go read those too bestie, the whole friend group is worth knowing 🫶✨

---

💀 reminder: everything above is exactly what the page says — the struct fields, the member meanings, the file path, all of it. do not freestyle the kernel. that's not the vibe we're going for.

---

and that's the whole page!! ngl it ate. this one shipped from ./include/linux/platform_data and it's dated October 2026 — so yeah, future-coded and flawless 💜🎀 bye bestie, see you in the next manpage ✨