STRUCT CEC_CAPS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME

struct cec_caps β€” the CEC capabilities structure, bestie. It's giving "here's what this device can actually do." ✨


✨ SYNOPSIS

struct cec_caps {
    char driver[32];
    char name[32];
    __u32 available_log_addrs;
    __u32 capabilities;
    __u32 version;
 };

πŸŽ€ Members

Okay so let's go through the members one by one, no skips, fr fr πŸ‘‘

  • driver β€” the name of the CEC device driver. That's your driver's whole identity, periodt.
  • name β€” the name of the CEC device. Heads up though: driver + name must be unique β€” together they're the one-of-a-kind combo, so don't be out here duplicating, iykyk 🫢
  • available_log_addrs β€” the number of available logical addresses.
  • capabilities β€” the capabilities of the CEC adapter. Literally the whole vibe check of what it can do πŸ’…
  • version β€” the version of the CEC adapter framework.
Quick little note bestie: available_log_addrs, capabilities and version are all __u32, and driver and name are char[32] each β€” the exact types matter, don't come for me 🌸

πŸ‘€ SEE ALSO

Peep the kernel file ./include/uapi/linux/cec.h, plus all these iconic siblings:


And that's the whole page, bestie β€” sourced from ./include/uapi/linux, stamped October 2026, living in the Kernel API Manual. Go forth and cap those CECs πŸ¦‹πŸ’–

πŸ“¦ where this page comes from