i3c_master_r...c_dev_locked(9)

📦 version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay so welcome to the Kernel API Manual, bestie — this page is i3c_master_r...c_dev_locked(9), and it's literally about i3c_master_reattach_i3c_dev_locked — reattaching an I3C device that got itself a brand new address. glow-up arc fr 💅

🦋 SYNOPSIS 🦋

int i3c_master_reattach_i3c_dev_locked (struct i3c_dev_desc *dev , u8
old_dyn_addr );

🎀 ARGUMENTS 🎀

  • dev — the I3C device descriptor you're reattaching, like the little guy's whole ID card 🪪
  • old_dyn_addr — the device's previous dynamic address, i.e. the address it had before the glow-up 👑

🌸 DESCRIPTION 🌸

so the way this works: this function reattaches an existing I3C device to the bus when its dynamic address has changed. it updates the bus address slot status accordingly, no cap:

  • Marks the new dynamic address as occupied by an I3C device ✅
  • Frees the old dynamic address slot if applicable 🗑️
⚠️ bestie this function must be called with the bus lock held in write mode. like, not optional. that's the rule. 🔒

🔥 RETURN 🔥

returns 0 on success 🎉 — or a negative error code if the reattachment fails (e.g. -EBUSY if the new address slot is not free 😭). yeah she'll tell you if the slot's taken, iconic of her honestly.

💜 SEE ALSO 💜

Kernel file ./drivers/i3c/master.c — go read it, iykyk 📖

and that's the whole page, bestie!! 🫶 this one's from ./drivers/i3c, stamped October 2026, page i3c_master_r...c_dev_locked(9) — go forth and reattach those devices responsibly 💖✨

📦 where this page comes from