drivers/media/cec/platform/seco

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.

keep-annotate conf=0.83 deploy=low replacement=none subsystem=media category=media-other
83%

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

3 files
929 source lines
5 commits, 5y
+36 / −51 lines added / removed, 5y
5 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 5 total · active in 4/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 0 commits · +0 −0 2021-07: 0 commits · +0 −0 2021-08: 0 commits · +0 −0 2021-09: 0 commits · +0 −0 2021-10: 0 commits · +0 −0 2021-11: 0 commits · +0 −0 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 2 commits · +28 −29 2022-03: 1 commit · +5 −17 2022-04: 0 commits · +0 −0 2022-05: 0 commits · +0 −0 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 1 commit · +2 −4 2023-04: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 0 commits · +0 −0 2023-08: 0 commits · +0 −0 2023-09: 0 commits · +0 −0 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 0 commits · +0 −0 2024-03: 0 commits · +0 −0 2024-04: 0 commits · +0 −0 2024-05: 0 commits · +0 −0 2024-06: 0 commits · +0 −0 2024-07: 0 commits · +0 −0 2024-08: 0 commits · +0 −0 2024-09: 1 commit · +1 −1 2024-10: 0 commits · +0 −0 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 0 commits · +0 −0 2025-05: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 2025-08: 0 commits · +0 −0 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 0 commits · +0 −0 2026-02: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    The driver still receives upstream fixes as of 2026-04-24 ('media: cec: seco: unregister adapter on IR probe failure').

  2. 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.

  3. 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.

  4. 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.