linux-drivers/
drivers/soc/rockchip

Rockchip RK3xxx/RK35xx SoC platform support

Low-level platform support for Rockchip's RK3xxx and RK35xx ARM systems-on-chip, covering the general register file, I/O voltage domain configuration, and thermal/power management. These SoCs power single-board computers (Radxa, Pine64, Orange Pi), Android TV boxes, Chromebooks, and embedded devices, with the newer RK3576 and RK3588 parts still sold new.

keep conf=0.89 deploy=medium replacement=none subsystem=soc category=platform-vendor
89%

recommendation

It should stay because these are the platform glue drivers (general register file, I/O domain voltage handling, and thermal/power management) that current Rockchip chips depend on, including the RK3576 and RK3588 still being sold into single-board computers, TV boxes, and embedded products in 2024–2025. Upstream maintenance is active, with bug fixes still landing in 2026, and there is no replacement in the tree.

repository signals

5 files
1,075 source lines
34 commits, 5y
+898 / −1,675 lines added / removed, 5y
25 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 34 total · active in 22/61 months
2021 2022 2023 2024 2025 2026 2021-04: 2 commits · +145 −107 2021-05: 0 commits · +0 −0 2021-06: 0 commits · +0 −0 2021-07: 0 commits · +0 −0 2021-08: 2 commits · +81 −9 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: 2 commits · +74 −0 2022-02: 0 commits · +0 −0 2022-03: 1 commit · +3 −3 2022-04: 4 commits · +149 −14 2022-05: 1 commit · +2 −0 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 2 commits · +49 −0 2022-09: 2 commits · +88 −13 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: 1 commit · +125 −35 2023-05: 1 commit · +27 −27 2023-06: 1 commit · +14 −0 2023-07: 1 commit · +0 −1,396 2023-08: 1 commit · +1 −1 2023-09: 2 commits · +2 −16 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: 2 commits · +42 −0 2024-06: 0 commits · +0 −0 2024-07: 0 commits · +0 −0 2024-08: 1 commit · +29 −1 2024-09: 0 commits · +0 −0 2024-10: 1 commit · +4 −4 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: 1 commit · +17 −18 2025-09: 1 commit · +14 −0 2025-10: 1 commit · +1 −0 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 2 commits · +28 −29 2026-02: 1 commit · +1 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    `drivers/soc/rockchip/grf.c` received a real bug-fix patch in March 2026 ('Add missing of_node_put() when returning'), showing ongoing upstream maintenance.

  2. rock-chips.com

    Rockchip marketed RK3576 in 2024 with Linux SDK support, indicating current-generation hardware still shipping around 2025.

  3. rock-chips.com

    Rockchip markets RK3588 with Android/Linux support and modern high-speed interfaces, supporting the case that the family remains relevant in new deployments.

codex reasoning notes (technical)

Local inspection via `exec_command` showed real SoC support drivers (`grf.c`, `io-domain.c`, `dtpm.c`), not test/docs/helpers only; `grf.c` already contains support tables for recent SoCs including RK3576 and RK3588. lore evidence came from `lore_file_timeline` on `drivers/soc/rockchip/grf.c` and `drivers/soc/rockchip/io-domain.c`; cited lore URL was returned directly by that tool. Rockchip product URLs were obtained via `web.search_query` and confirmed with `web.open`. No natural successor driver is visible in-tree; these are platform-specific support blocks still needed for current Rockchip SoCs. A targeted removal/deprecation search was attempted (`lore_regex`, then `lei`) but produced no usable removal evidence, so there is no basis to escalate beyond keep.