devm_extcon...notifier_all(9)

📦 version 7.3.1, in nixpkgs unstable

💅 devm_extcon_register_notifier_all(9)

okay bestie, this one lives in the Kernel API Manual (yes, the kernel has a manual, she's fancy like that) — let's get into it ✨

🦋 NAME

devm_extcon_register_notifier_all — and ngl, the original page leaves the description blank, so we're just vibing with the function name itself. No cap, that's literally all it says. 🙈

✨ SYNOPSIS

int devm_extcon_register_notifier_all (struct device *dev , struct extcon_dev *edev , struct notifier_block *nb );

🎀 ARGUMENTS

  • dev — the device that owns the extcon device being created 👑
  • edev — the extcon device itself, the main character
  • nb — a notifier block to be registered, aka the little thing you're signing up for the notifications

🌸 DESCRIPTION

  • Resource-managed extcon_register_notifier_all

So here's the tea ☕: this function handles the notifier of the extcon device automatically for you, using device resource management — which is iconic because it simplifies all the controlling of unregistering the notifier of the extcon device. Like, you don't have to manually clean up after yourself, the devres machinery does it. 💅

Want more info? Go refer to that function (extcon_register_notifier_all) — this page is just the managed wrapper, iykyk. 🫶

Returns 0 if success, or a negative error number if failure. 😭

fr fr, negative = something went wrong, don't ignore it.

🔥 SEE ALSO

Kernel file ./drivers/extcon/devres.c plus these besties:

🌈 sign-off 🎀

This page comes to you from ./drivers/extcon (that's the source path, periodt), dated October 2026, and it's part of the Kernel API Manual because of course it is. Slay, go register that notifier. ⭐💜

devm_extcon...notifier_all(9)

📦 where this page comes from