module_usb_composite_driver(9)
π¦ module_usb_composite_driver(9) π¦
Okay bestie, welcome to the Kernel API Manual entry for module_usb_composite_driver(9) β the macro that handles registering a USB gadget composite driver when your module is lowkey chill in init/exit. Letβs get into it. β¨
πΈ NAME πΈ
module_usb_composite_driver β helper macro for registering a USB gadget composite driver. Thatβs the whole name-card vibe, and honestly? Iconic. π
β¨ SYNOPSIS β¨
module_usb_composite_driver (__usb_composite_driver );
π ARGUMENTS π
__usb_composite_driverβ ausb_composite_driverstruct. Yep, thatβs the argument, bestie: theusb_composite_driverstruct gets handed over, and the macro does its thing. π«Ά
π DESCRIPTION π
Okay so picture this: youβve got a USB gadget composite driver, and it does not do anything special in module init/exit. This macro is your helper for exactly that situation. It eliminates a lot of boilerplate β like, the boring copy-paste glue is gone, slay. π₯
Each module may only use this macro once, and calling it replacesmodule_initandmodule_exit. Not me emphasizing this, but bestie, it matters. ππ
π¦ SEE ALSO π¦
- Kernel file
./include/linux/usb/composite.hstruct β yes, the page calls out that kernel file, and thestructword is right there in the mix. struct usb_os_desc_ext_prop(9)struct usb_os_desc(9)struct usb_os_desc_table(9)struct usb_function(9)struct usb_configuration(9)struct usb_composite_driver(9)struct usb_composite_dev(9)
Cute sign-off time, bestie: this pageβs source/version vibes come from ./include/linux/usb, the date is October 2026, and it signs itself module_usb_composite_driver(9). Thatβs the footer, but make it fashion. ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms