i3c_master_...c_dev_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ i3c_master_add_i3c_dev_locked β€” kernel API manual energy πŸŽ€

okay so bestie, welcome to the Kernel API Manual ✨ this one's short but she's important, and honestly the vibe is "quietly running the whole party" 🫢


✨ NAME ✨

i3c_master_add_i3c_dev_locked β€” literally the function that adds an I3C slave to the bus πŸ’… no cap, that's the whole job description.


🌸 SYNOPSIS 🌸

void i3c_master_add_i3c_dev_locked (struct i3c_master_controller *master
, u8 addr );

she's a void, she returns nothing, she simply does πŸ’– the way that this function just shows up and makes a device exist? iconic.


πŸ¦‹ ARGUMENTS πŸ¦‹

  • master β€” the master controller used to send frames on the bus. think of her as the one holding the aux cord 🎧 every frame goes through her.
  • addr β€” the I3C slave dynamic address assigned to the device 🏷️ this is the device's little name tag at the party.

πŸ‘‘ DESCRIPTION πŸ‘‘

so what she actually does: this function instantiates an I3C device object and adds it to the I3C device list πŸŽ€ and the best part? all device information is automatically retrieved using standard CCC commands ✨ not me, not you, the CCC commands are doing the heavy lifting. main character energy fr fr.

🚨 IMPORTANT, like actually important: this function must be called with the bus lock held in write mode πŸ’€ do not skip this. the lock is not decorative. she is not a suggestion. hold the lock, in write mode, periodt.

ngl it's giving "small function, big responsibilities" 😭 respect her.


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/i3c/master.c πŸ’« and the whole friend group:

like, that's a whole group chat right there and every single one of them is invited πŸ“²πŸ’–


✨ that's the whole page bestie ✨ this little gem lives in the ./drivers/i3c corner of the kernel tree 🌈 and she was dated October 2026 πŸŽ€ go forth, hold that write lock, and add your devices with confidence πŸ’…πŸ’œ

πŸ“¦ where this page comes from