i3c_dev_disable_ibi_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… i3c_dev_disable_ibi_locked(9) β€” from the Kernel API Manual, bestie

okay so this one lives in the Kernel API Manual and it's called i3c_dev_disable_ibi_locked β€” say that five times fast, I dare you 😭 it's giving "locked" energy and honestly? iconic.


✨ NAME ✨

i3c_dev_disable_ibi_locked β€” literally just turning off IBIs coming from one specific device. That's the whole vibe. πŸŽ€


🌸 SYNOPSIS 🌸

int i3c_dev_disable_ibi_locked (struct i3c_dev_desc *dev );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the device on which IBIs should be disabled. yeah. that one. the specific one. πŸ‘‘

πŸ’– DESCRIPTION πŸ’–

so what this does is, it disables IBIs coming from a specific device β€” one device, not all of them, don't be messy β€” and then it waits for all pending IBIs to be processed. like it doesn't just dip, it makes sure everything queued up gets handled first. patient queen behavior honestly 🫢


πŸ”₯ CONTEXT πŸ”₯

bestie. read this twice. it must be called with mutex_lock(dev->desc->ibi_lock) held. no lock, no call, that's the rule πŸ’€

⭐ RETURN ⭐

0 in case of success, and a negative error code otherwise. (the original page says "error core" 😭 typo era, but you know what it means β€” negative code, no cap.)


πŸ’œ SEE ALSO πŸ’œ

Kernel file ./drivers/i3c/master.c, plus a whole friend group of functions β€” all of them, here we go, no skipping, I promised πŸ™ˆ


and that's the whole page, bestie, you ate that πŸ’…βœ¨

sign-off time πŸŽ€ this lil beauty comes from ./drivers/i3c, dated October 2026, and it'll always be i3c_dev_disable_ibi_locked(9) to me πŸ¦‹πŸ’œ

πŸ“¦ where this page comes from