drivers/clk/actions

Actions Semi OWL S500/S700/S900 SoC clock controllers

Provides clock and PLL management for Actions Semi's OWL-family ARM SoCs, specifically the S500, S700, and S900 chips that powered a handful of mid-2010s single-board computers and Android tablets, most notably the 96Boards Bubblegum-96 developer board.

keep-annotate conf=0.74 deploy=low replacement=none subsystem=clk category=infrastructure
74%

recommendation

Worth keeping but documenting its niche, because the hardware family is small and legacy-skewed (the most visible product is the 96Boards Bubblegum-96 developer board built around the S900) yet the code is clearly still maintained: it was touched as part of a treewide clk cleanup in August 2025 and had a real bug fix backported to stable in 2022. There is no replacement driver possible since this is the SoC-specific clock provider, so removing it would break the boards that still exist.

repository signals

22 files
3,732 source lines
22 commits, 5y
+171 / −142 lines added / removed, 5y
10 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 22 total · active in 9/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 5 commits · +64 −34 2021-07: 0 commits · +0 −0 2021-08: 0 commits · +0 −0 2021-09: 1 commit · +0 −1 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 · +33 −30 2022-03: 0 commits · +0 −0 2022-04: 1 commit · +1 −1 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: 0 commits · +0 −0 2023-04: 0 commits · +0 −0 2023-05: 3 commits · +24 −11 2023-06: 0 commits · +0 −0 2023-07: 2 commits · +2 −6 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: 0 commits · +0 −0 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: 5 commits · +35 −24 2025-09: 0 commits · +0 −0 2025-10: 1 commit · +7 −7 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 2 commits · +5 −28 2026-02: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    The directory still receives upstream touches in 2025; owl-common.c was part of a 2025 clk treewide cleanup series, so it is not abandoned.

  2. lore.kernel.org

    The Actions clock code had a real bug fix backported to stable in 2022, indicating maintained deployed users rather than dead code.

  3. 96boards.org

    Bubblegum-96 is a real Actions S900 board, tying the driver family to shipping developer hardware.

  4. ucrobotics.com.tw

    A current retailer page still lists Bubblegum-96 hardware, supporting that at least some Actions S900 hardware remained sold new into the 2025 timeframe, albeit as a niche board.

codex reasoning notes (technical)

Real driver directory: Kconfig says 'Clock driver for Actions Semi SoCs' and SoC-specific objects exist for S500/S700/S900. lore_file_timeline on drivers/clk/actions/owl-common.c showed 23 matches with newest touch on 2025-08-13 and no removal signal in returned events. lore_activity on drivers/clk/actions/owl-s900.c surfaced stable backports including the 2022 sentinel fix, showing ongoing maintenance for deployed systems. web search returned the 96Boards Bubblegum-96 product page and a current uCRobotics sales page; that supports niche ongoing availability, but only for older dev boards, so deployments today look low rather than none. No natural replacement driver exists because this is the SoC-specific CMU/clock provider for Actions OWL parts. Recommendation is keep-annotate: upstream attention exists, removal evidence was not found, but the hardware family appears niche and legacy-skewed.