SECO and UDOO x86 board HDMI-CEC controller
An integrated HDMI-CEC controller found on SECO-built x86 single-board computers, including the UDOO X86 family, that lets the board send and receive HDMI remote-control commands to and from a connected TV or display. It is bound via the ACPI ID CEC00001 and targets industrial and maker-oriented embedded systems sold from the late 2010s onward.
recommendation
Worth keeping but documenting its niche audience: this supports HDMI Consumer Electronics Control on a small family of SECO and UDOO x86 single-board computers aimed at industrial and maker users. Upstream activity is still alive (a bug-fix patch landed in 2026), and SECO continues to sell compatible boards like the UDOO X86 II Ultra, but real-world deployments are modest, so a note about its specialized scope is appropriate.
repository signals
sources
- lore.kernel.org
The driver still receives upstream fixes as of 2026-04-24 ('media: cec: seco: unregister adapter on IR probe failure').
- cateee.net
LKDDb maps this driver to SECO Boards HDMI CEC, ACPI ID CEC00001, platform device 'secocec', and shows it remains present in current kernel series.
- shop.seco.com
SECO Shop listed the UDOO X86 II ULTRA board as available, indicating at least some SECO/UDOO hardware using this support stack was still sold new around 2025-2026.
- seco.com
The UDOO X86 II manual documents an HDMI connector with a CEC line on a SECO board family associated with this driver.
codex reasoning notes (technical)
Real driver: local file inspection via shell showed a platform CEC driver for 'SECO X86 Boards'. lore_file_timeline on drivers/media/cec/platform/seco/seco-cec.c showed fresh upstream activity, including a 2026-04-24 bug-fix patch, and no visible removal trend in returned history, so removal/deprecation is not supported. Web search returned LKDDb confirming ACPI CEC00001/platform secocec binding, plus SECO Shop/manual pages showing compatible SECO/UDOO HDMI-CEC-capable boards still marketed; that points to ongoing but niche industrial/maker deployments rather than broad volume. Chosen 'keep-annotate' because deployments appear low and hardware family is specialized, but upstream maintenance is still active.