STRUCT I3C_DEV_BOARDINFO(9)

✨ struct i3c_dev_boardinfo(9) ✨

okay bestie, this is the struct i3c_dev_boardinfo page from the Kernel API Manual — it's literally just one struct, but she's an important one 🎀

🌸 NAME 🌸

struct i3c_dev_boardinfo — I3C device board information 💅

⭐ SYNOPSIS ⭐

struct i3c_dev_boardinfo {
    struct list_head node;
    u8 init_dyn_addr;
    u8 static_addr;
    u8 static_addr_method;
    u64 pid;
    struct fwnode_handle *fwnode;
 };

🦋 Members 🦋

• node — this one's the little handle used to insert your boardinfo object into the I3C boardinfo list. list bookkeeping, that's it, that's her job 💖
• init_dyn_addr — the initial dynamic address that the FW requested. And ngl, there's no guarantee the device will actually end up using this address — but the kernel tries its best to assign this specific address to the device. so like… she's manifesting it, ok? 🫶
• static_addr — the static address the I3C device listens on before the master has assigned it a dynamic address. This gets used during bus initialization to assign it a specific dynamic address before starting DAA (Dynamic Address Assignment). pre-glow-up address, iconic 💫
• static_addr_method — a bitmap describing which methods of Dynamic Address Assignment from a Static Address are supported by this I3C Target. A value of 1 in a bit position means the target supports that method, and a value of 0 means it does not. So: Bit 0: SETDASA, Bit 1: SETAASA, and all other bits are reserved 🔥
• pid — the I3C Provisioned ID exposed by the device. It's a unique identifier that may be used to attach boardinfo to i3c_dev_desc when the device does not have a static address. her literal fingerprint, iykyk 👑
• fwnode — the Firmware node (DT or ACPI) in case the device has been described in firmware 🌈

💜 Description 💜

This structure is used to attach board-level information to an I3C device. And bestie, hear me: not all I3C devices connected on the bus will have a boardinfo. It's only needed if you want to attach extra resources to a device or assign it a specific dynamic address. lowkey exclusive, not everyone gets an invite 💅

🎀 SEE ALSO 🎀

Kernel file ./include/linux/i3c/master.h

• struct i3c_i2c_dev_desc(9)
• struct i2c_dev_boardinfo(9)
• struct i2c_dev_desc(9)
• struct i3c_ibi_slot(9)
• struct i3c_device_ibi_info(9)
• struct i3c_dev_desc(9)
• struct i3c_device(9)
• enum i3c_bus_mode(9)
• enum i3c_open_drain_speed(9)
• enum i3c_addr_slot_status(9)
• struct i3c_bus(9)
• struct i3c_master_controller_ops(9)
• struct i3c_master_controller(9)
• i3c_bus_for_each_i2cdev(9)
• i3c_bus_for_each_i3cdev(9)
• struct i3c_dma(9)
• i3c_dev_get_master_data(9)
• i3c_dev_set_master_data(9)
• i2c_dev_get_master_data(9)
• i2c_dev_set_master_data(9)
• i3c_dev_get_master(9)
• i2c_dev_get_master(9)
• i3c_master_get_bus(9)

that's the whole page, no cap 😭 this queen lives over in ./include/linux/i3c, and she's stamped October 2026 in the Kernel API Manual — go read the source bestie, mwah 🧚💖⭐