__auxiliary_driver_register(9)

💖 NAME 💖

okay bestie, welcome to the __auxiliary_driver_register(9) page from the Kernel API Manual ✨ this one is literally about registering a driver for auxiliary bus devices, and it's giving very important kernel business 💅

✨ SYNOPSIS ✨

int __auxiliary_driver_register (struct auxiliary_driver *auxdrv ,
       struct module *owner , const char *modname );

🎀 ARGUMENTS 🎀

• auxdrv — the auxiliary_driver structure, aka the driver thing you're handing over 🫶
• owner — the owning module/driver 👑
• modname — the KBUILD_MODNAME for the parent driver 🏷️

💅 DESCRIPTION 💅

so here's the tea: the expectation is that users will call the "auxiliary_driver_register" macro so that the caller's KBUILD_MODNAME is automatically inserted for the modname parameter ✨

only if a user requires a custom name would this version be called directly. no cap, that's the whole situation fr fr 💖

🦋 SEE ALSO 🦋

go check these icons too, bestie 👀

• kernel file ./drivers/base/auxiliary.c
• PURPOSE(9)
• USAGE(9)
• EXAMPLE(9)
• auxiliary_device_init(9)
• __auxiliary_device_add(9)
• auxiliary_driver_unregister(9)
• auxiliary_device_create(9)
• auxiliary_device_destroy(9)
• __devm_auxiliary_device_create(9)
• dev_is_auxiliary(9)

source check for the footer vibes: this page is filed under ./drivers/base, dated October 2026, and it's the __auxiliary_driver_register(9) manual entry — bye bestie, go register responsibly 💅✨