i3c_device_request_ibi(9)

💅 i3c_device_request_ibi(9) 💅

okay so bestie, welcome to the Kernel API Manual — this page is literally about i3c_device_request_ibi(9), and it’s giving “prep the IBI resources before the enabling era” energy. no cap, the vibe check is: request first, enable later ✨

✨ NAME ✨

i3c_device_request_ibi — Request an IBI

🦋 SYNOPSIS 🦋

int i3c_device_request_ibi (struct i3c_device *dev , const struct
       i3c_ibi_setup *req );

🌸 ARGUMENTS 🌸

• dev — the device for which we should enable IBIs. main character device energy, fr fr.
• req — the setup requested for this IBI.

🎀 DESCRIPTION 🎀

okay so this function is responsible for pre-allocating all resources needed to process IBIs coming from dev. think of it as packing the little IBI survival kit before the party starts 🎒✨ — iconic prep behavior, lowkey.

when this function returns, the IBI is not enabled until i3c_device_enable_ibi is called. so do not get it twisted, bestie: requesting the setup is not the same as flipping the enable switch. periodt 💅

⭐ RETURN ⭐

0 in case of success, a negative error core otherwise. yes, “core” — not me editing the manpage lore, i’m just keeping every detail 💀

🔥 SEE ALSO 🔥

• Kernel file ./drivers/i3c/device.c
• i3c_device_do_xfers(9)
• i3c_device_do_setdasa(9)
• i3c_device_get_info(9)
• i3c_device_disable_ibi(9)
• i3c_device_enable_ibi(9)
• i3c_device_free_ibi(9)
• i3cdev_to_dev(9)
• i3c_device_match_id(9)
• i3c_device_get_supported_xfer_mode(9)
• i3c_driver_register_with_owner(9)
• i3c_driver_unregister(9)

mwah 💋 this page lives under ./drivers/i3c, is dated October 2026, and it’s serving i3c_device_request_ibi(9) realness. bye bestie, go pre-allocate those resources 🫶