rio_request_inb_dbell(9)

📦 version 7.3.1, in nixpkgs unstable

hey bestie 💖 you're looking at rio_request_inb_dbell(9) from the Kernel API Manual — the page where we request inbound doorbell message service 🎀

🌸 NAME 🌸

rio_request_inb_dbell — request inbound doorbell message service 🦋

✨ SYNOPSIS ✨

int rio_request_inb_dbell (struct rio_mport *mport , void *dev_id , u16
start , u16 end , void (*dinb) (struct rio_mport * mport, void *dev_id,
u16 src, u16 dst, u16 info) );

🎀 ARGUMENTS 🎀

  • mport — the RIO master port from which to allocate the doorbell resource 🌈
  • dev_id — device specific pointer to pass on event 🫶
  • start — doorbell info range start ✨
  • end — doorbell info range end 💖
  • dinb — callback to execute when doorbell is received 💅 its type is void (*dinb) (struct rio_mport * mport, void *dev_id, u16 src, u16 dst, u16 info)

👑 DESCRIPTION 👑

okay so here's the tea ☕: rio_request_inb_dbell requests ownership of an inbound doorbell resource and binds a callback function to the resource.

Returns 0 if the request has been satisfied. periodt 💅

👀 SEE ALSO 👀

Kernel file ./drivers/rapidio/rio.c is where it's at, and the whole see-also squad is right here 🫶:

and that's the page, bestie 🫶 — source/version ./drivers/rapidio, date October 2026, page rio_request_inb_dbell(9), signing off with main character energy 💅✨

📦 where this page comes from