devm_pse_con...ler_register(9)

📦 version 7.3.1, in nixpkgs unstable

💅 devm_pse_con...ler_register(9) — from the Kernel API Manual, bestie

okay so this one is a kernel API page (yes, the Kernel API Manual, that's the whole vibe) and it's genuinely so straightforward you're gonna slay it. it's about registering a PSE controller, but the ✨managed✨ version. let's go 💖

✨ NAME ✨

devm_pse_controller_register — the resource managed glow-up of pse_controller_register(). literally the same thing but with devm doing the cleanup for you, no cap 🫶

🎀 SYNOPSIS 🎀

int devm_pse_controller_register (struct device *dev , struct pse_controller_dev *pcdev );

🌸 ARGUMENTS 🌸

  • dev — the device that's registering this PSE controller. like, this is the main character doing the registering 👑
  • pcdev — a pointer to the initialized PSE controller device. key word: initialized. it's gotta be ready before you hand it over, fr fr

🦋 DESCRIPTION 🦋

okay so this is the managed version of pse_controller_register. for PSE controllers registered through this function, pse_controller_unregister gets called automatically on driver detach. like, you don't have to remember to clean up — devm handles it. iconic behavior honestly 💅

psst — for more info, go read pse_controller_register. this one is just the ✨managed✨ edition.

⭐ RETURN ⭐

  • 0 on success
  • a failure value on error 😭

(it's giving very simple, very demure)

🌈 SEE ALSO 🌈

kernel file: ./drivers/net/pse-pd/pse_core.c — go read the source bestie, iykyk 🔥

and the whole friend group, in the order the page gives them:

that's the whole page, babes 🫶 go register your controller, the devm way, and don't forget to read the source 💅

sign-off szn 🎀 — this one lives over in ./drivers/net/pse-pd, dated October 2026, and the page footer still calls it devm_pse_con...ler_register(9) (the terminal truncation is just the man page being extra, not you misreading it, i promise 😭). mwah 💋

📦 where this page comes from