cec_notifier_get_conn(9)
π cec_notifier_get_conn β like, the whole notifier situation π
okay so bestie, welcome to the Kernel API Manual section for cec_notifier_get_conn(9) β yes that (9) is the section number, it's giving very "I live in the kernel docs" energy and we respect it π«Ά
β¨ NAME β¨
cec_notifier_get_conn β find or create a new cec_notifier for the given device and connector tuple π
π¦ SYNOPSIS π¦
struct cec_notifier * cec_notifier_get_conn (struct device *hdmi_dev ,
const char *port_name );
like literally that's the whole signature, no notes π
πΈ ARGUMENTS πΈ
hdmi_devβ the device that sends the events π this is the one doing the most, main character energy frport_nameβ the connector name from which the event occurs β¨ iykyk
π DESCRIPTION π
okay so here's the vibe check on what actually happens when you call this π
If a notifier for device dev already exists, then it just increases the refcount and hands you back that notifier. Reuse era, environmentally friendly, we love to see it π
If it doesn't exist? No problem bestie, it allocates a brand new notifier struct and returns a pointer to that new struct. Fresh out of the box, brand new, iconic π
And if the memory could not be allocated, it returns NULL. π that's the "it's giving out of memory" moment, so like, always check your return value ngl
π SEE ALSO π
- Kernel file
./drivers/media/cec/core/cec-notifier.cβ go read the source bestie, it's all there ππ
lowkey important: this returns NULL on allocation failure, so don't just raw-dog the pointer without checking, fr fr π
and that's the page!! brought to you by the ./drivers/media/cec/core gang, dated October 2026, filed under cec_notifier_get_conn(9) β slay, periodt, go forth and notify π
β¨ππ§π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms