extcon_dev_register(9)

📦 version 7.3.1, in nixpkgs unstable

💖 extcon_dev_register(9) — Kernel API Manual 💖

okay so bestie, this one is a kernel API page — extcon_dev_register(9), straight out of the Kernel API Manual — and it's literally the moment your new extcon device gets ✨registered✨ into existence. Let's get into it 🫶

🌸 NAME 🌸

extcon_dev_register — Register an new extcon device 👑

(yes the original says "an new", we're keeping that energy, it's iconic 💅)

🦋 SYNOPSIS 🦋

int extcon_dev_register (struct extcon_dev *edev );

🎀 ARGUMENTS 🎀

  • edev — the extcon device that's about to be registered, bestie. this is the main character of the whole call 🌟

✨ DESCRIPTION ✨

okay so here's the tea 🍵 among all the members of the edev struct, please set the "user initializing data" — but do not set the values of the "internal data", because those get initialized by this function itself. like, this function handles its own business, don't touch it 🙈

📌 also note: before you call this function, you have to allocate the memory of an extcon device by using extcon_dev_allocate. no allocation, no registration, no cap. and the extcon dev should include the supported_cable information too — that's not optional, that's the vibe check 💀

Returns 0 if it slays (success) or an error number if it fails 😭

🔥 SEE ALSO 🔥

Kernel file ./drivers/extcon/extcon.c — plus the whole friend group:

mwah 💋 that's the whole page, and it lives at ./drivers/extcon with the date October 2026 — so go forth, register your devices, and remember: set the user data, let the kernel handle the internals. slay 💜✨

📦 where this page comes from