i3c_dev_request_ibi_locked(9)

📦 version 7.3.1, in nixpkgs unstable

💅 i3c_dev_request_ibi_locked(9) 💅

okay so bestie, welcome to the Kernel API Manual — this one's about i3c_dev_request_ibi_locked, and it's genuinely such a vibe once you get it. let's go 🎀

✨ NAME ✨

i3c_dev_request_ibi_locked — request an IBI 🦋

🌸 SYNOPSIS 🌸

int i3c_dev_request_ibi_locked (struct i3c_dev_desc *dev , const struct
       i3c_ibi_setup *req );

like, that's the whole signature, no notes 💅

🎀 ARGUMENTS 🎀

  • dev — the device we should enable IBIs for, bestie. that's the main character of this whole function ngl.
  • req — the setup requested for this IBI. it's giving "here's my whole plan" energy ✨

💖 DESCRIPTION 💖

okay so this function is literally responsible for pre-allocating all the resources you'll need to process IBIs coming from dev. it's doing the prep work so future-you doesn't have to 😭🫶

but listen — and this is the important part — when this function returns, the IBI is not enabled yet. it stays un-enabled until you call i3c_device_enable_ibi. so like... don't be out here acting surprised that nothing's firing yet, that's literally the deal, no cap 🔥

⭐ CONTEXT ⭐

must be called with mutex_lock(dev->desc->ibi_lock) held. periodt. 🔒 like if you're not holding that lock, you're not doing this, that's the vibe check 💀

🌈 RETURN 🌈

returns 0 in case of success, and a negative error core otherwise (yes, core — that's what it says, i'm just the messenger bestie 😭🙈 — obviously it means error code, but we keep it 100% accurate here).

🦋 SEE ALSO 🦋

the whole squad, and i mean the whole squad 👑 — plus the kernel file ./drivers/i3c/master.c:

ngl that's a lot of friends but every single one of them earned their spot 💅

and that's the page!! mwah 🫶 from ./drivers/i3c, dated October 2026 — go forth and lock your mutex, bestie 🌸✨🦋

📦 where this page comes from