phy_module_driver(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… phy_module_driver β€” a Kernel API Manual moment (yes, from phy_module_driver(9), we're fancy)

okay so bestie, picture this: you wrote a PHY driver, it's gorgeous, it's iconic, and now you need the kernel to actually register it. that's the whole job of this macro. it's the "just do the normal thing for me" button. ✨


🌸 NAME 🌸

phy_module_driver β€” the helper macro for registering PHY drivers. that's it. that's the name. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

phy_module_driver (__phy_drivers , __count );

literally just drop it in your file like that, no cap.


πŸ’– ARGUMENTS πŸ’–

  • __phy_drivers β€” the array of PHY drivers you wanna register. your whole little squad of drivers, in array form. πŸ‘‘
  • __count β€” the number of members in that array. yes you have to count them. no the macro won't do it for you. it's giving "do your own homework". 😭

πŸ”₯ DESCRIPTION πŸ”₯

so this is the helper macro for PHY drivers that don't do anything special in module init/exit. like, nothing extra, no little send-off ritual, just vibes and registration. 🫢

⚠️ each module may only use this macro once. one time. single use. and calling it replaces module_init and module_exit β€” so don't go doubling up, that's not the move. πŸ’€

⭐ SEE ALSO ⭐

the extended universe, ok? every single one of these, because the kernel is a whole friend group and they all show up to the party 🧚:


and that's the page, bestie!! 🌈 source lives at ./include/linux, dated October 2026, filed under phy_module_driver(9) β€” go forth and register your drivers, you absolute main character πŸ’œπŸ‘‘πŸ“

πŸ“¦ where this page comes from