HDMI CEC: What? Why? How?
summary
HDMI exposes a CEC pin carrying ~400 bits/sec for device control; a kernel 4.8 framework provides a shared header, adapter ops and an API that handles asynchronous replies, logical/physical address reclaiming, and common protocol quirks. Utilities include ccctl, cec-compliance and a cec-follower reference; a virtual adapter emulates 400 bps for testing. Adapters typically take ~2 days to add; compliance tests show many real devices fail; framework is functional in staging but needs error‑handling and corner‑case cleanup.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:40Consumer Electronics Control
- 3:46Physical Address
- 4:44Logical Address
- 6:17Topology Example
- 7:20End-User Features
- 9:03Supporting Features
- 18:12CEC Framework
- 24:12CEC Adapter Driver
- 28:42CEC API
- 30:17CEC Utilities
- 36:09Resources
related talks
45mV4L2 & CEC Status Report
42mExtended Display Identification Data (EDID): Problems, Pitfalls and Complications
40mHDMI 4k Video: Lessons Learned
45mImproving the Linux Display Stack Reliability
29mCXL HDM-DB support for Linux
23mCXL hotplug: spec to reality
18mStateless HEVC Decoding in Mainline Linux: The Rocky Road to Becoming a Stable API
43mUCSI, TCPM, PD, AltModes: Demystifying USB-C and Its Support in Linux