sunxi_rsb_driver_register(9)

💅 sunxi_rsb_driver_register(9) — from the Kernel API Manual, bestie

okay so real talk, this one's a little function with a big job, and it lives in the Kernel API Manual (yes, the (9) is the manual section, we stan a section number). get comfy, this is gonna be quick but it's important 🫶

✨ NAME ✨

sunxi_rsb_driver_register — the way you tell the RSB core "hey bestie, here's a driver, please associate it, ty" 💖

🌸 SYNOPSIS 🌸

int sunxi_rsb_driver_register (struct sunxi_rsb_driver *rdrv );

that return type is int, and the one and only thing you hand over is a pointer to a struct sunxi_rsb_driver named rdrv. slay, one argument, we love a low-effort call ✨

🎀 ARGUMENTS 🎀

• rdrv — the device driver that's getting associated with the slave-device. that's it, that's the whole vibe check. this is the driver, and it wants to be hooked up to its slave-device 🦋

💫 DESCRIPTION 💫

so what actually happens? this API registers the client driver with the RSB framework. no cap, that's the whole function's personality 🔥

and where do you call it? it's typically called from the driver's module-init function — like, that's its natural habitat, that's where it belongs, main character energy honestly 👑

lowkey important: this is the register side of things. the unregister side exists and it's linked down below, so don't be a stranger to it when your module goes bye-bye 🙈

🌈 SEE ALSO 🌈

• Kernel file ./drivers/bus/sunxi-rsb.c — where the actual source lives, go read it, it's giving iconic
• sunxi_rsb_device_create(9)
• sunxi_rsb_device_unregister(9)

and that's the page!! 💜 remember the whole thing came out of ./drivers/bus, dated October 2026, so if anyone asks where this lore dropped, that's the source and the date, periodt 🎀✨🧚