peci_driver_register(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… peci_driver_register(9) β€” like, the Kernel API Manual, bestie ✨

okay so this is peci_driver_register, straight out of the Kernel API Manual, and it's genuinely one of the shorter ones so we can absolutely get through this together 🫢


πŸŽ€ NAME πŸŽ€

peci_driver_register β€” the function that registers a PECI driver. that's it, that's the vibe. πŸ‘‘


✨ SYNOPSIS ✨

peci_driver_register (driver );

(no cap, the spacing in there is exactly how it's written, don't come for me πŸ’€)


🌸 ARGUMENTS 🌸

  • driver β€” the driver you're registering. yes, the one right there. that's the whole argument. she's simple, she's iconic πŸ’–

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea β˜• β€” if your PECI driver doesn't need to do anything special in module init, you should not be hand-rolling this call. instead, use the convenience macro module_peci_driver, which handles it for you. it's giving "let the macro cook" πŸ”₯

lowkey the whole point: use module_peci_driver unless you genuinely have something extra to do at init time. iykyk 🧚

⭐ RETURN ⭐

  • zero on success πŸŽ‰
  • otherwise, a negative error code 😭

that's the entire return contract, fr fr.


🌈 SEE ALSO 🌈

  • Kernel file ./drivers/peci/internal.h
  • struct peci_device_id(9)
  • struct peci_driver(9)
  • module_peci_driver(9)

go read those next, bestie, they're literally right there πŸ’œ


okay and like, source/version note for the record: this page lives under ./drivers/peci and it's dated October 2026 β€” so yeah, future-dated manual page, main character energy only πŸ’…βœ¨ slay, go register that driver, periodt πŸŽ€

πŸ“¦ where this page comes from