drivers/clk/xilinx

AMD/Xilinx Clocking Wizard and Zynq/Versal SoC clock controllers

Clock generation blocks found inside AMD (formerly Xilinx) FPGAs and adaptive SoCs, including the configurable Clocking Wizard IP, the video codec unit on Zynq UltraScale+ EV chips, and the clock wizard on Versal Adaptive SoCs. These parts are widely used in current embedded, industrial, automotive, and aerospace designs built around Xilinx programmable logic.

keep conf=0.93 deploy=medium replacement=none subsystem=clk category=infrastructure
93%

recommendation

It should stay in the kernel because the hardware is still actively sold by AMD for new designs across the Clocking Wizard IP, Zynq UltraScale+ MPSoC, and Versal Adaptive SoC families, and the code is being actively developed upstream as recently as a February 2026 patch series. There is no replacement driver, and removal would break support for current shipping silicon.

repository signals

4 files
2,024 source lines
30 commits, 5y
+1,759 / −465 lines added / removed, 5y
14 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 30 total · active in 16/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: 0 commits · +0 −0 2022-03: 0 commits · +0 −0 2022-04: 4 commits · +659 −4 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: 1 commit · +6 −10 2022-10: 2 commits · +3 −2 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: 3 commits · +208 −34 2023-04: 0 commits · +0 −0 2023-05: 2 commits · +6 −1 2023-06: 0 commits · +0 −0 2023-07: 1 commit · +1 −1 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: 1 commit · +536 −92 2024-01: 0 commits · +0 −0 2024-02: 1 commit · +1 −1 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: 1 commit · +1 −1 2024-08: 0 commits · +0 −0 2024-09: 6 commits · +179 −218 2024-10: 0 commits · +0 −0 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 1 commit · +69 −52 2025-02: 2 commits · +31 −2 2025-03: 0 commits · +0 −0 2025-04: 0 commits · +0 −0 2025-05: 0 commits · +0 −0 2025-06: 1 commit · +1 −1 2025-07: 1 commit · +18 −14 2025-08: 2 commits · +39 −31 2025-09: 1 commit · +1 −1 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

    Upstream activity is current: the directory's clock-wizard driver saw a feature patch series in February 2026, which argues against deprecation.

  2. amd.com

    Clocking Wizard remains a current AMD IP offering, indicating the associated Linux driver targets hardware/IP still marketed for new designs.

  3. amd.com

    Zynq UltraScale+ MPSoCs, including EV variants with integrated video codec, are still marketed and described as long-lived products, matching the VCU-related driver scope.

  4. amd.com

    Versal Adaptive SoCs are current AMD products; the driver explicitly matches "xlnx,versal-clk-wizard", so it covers hardware still used in new deployments.

codex reasoning notes (technical)

Local file inspection via exec_command showed active platform drivers for "xlnx,clocking-wizard", "xlnx,versal-clk-wizard", and "xlnx,vcu", so this is a real hardware-driver directory, not a helper library. The lore URL was obtained with lore_activity(file="drivers/clk/xilinx/clk-xlnx-clock-wizard.c"), which returned active 2026 patch traffic; that is strong evidence the code is maintained rather than pending removal. The AMD URLs were obtained with web search on amd.com and show the relevant IP/SoC families are still sold for current embedded designs. Given active upstream development plus ongoing product availability, there is no natural replacement driver and the right disposition is to keep it.