Re: [PATCH v3 2/3] dt-bindings: clock: Add rk3576 clock definitions and documentation
From: "Rob Herring (Arm)" <robh@kernel.org>
Date: 2024-08-08 17:17:30
Also in:
linux-clk, linux-devicetree, linux-rockchip, lkml
On Thu, 08 Aug 2024 12:20:57 -0400, Detlev Casanova wrote:
Add clock ID defines for rk3576. Compared to the downstream bindings written by Elaine, this uses continous gapless clock IDs starting at 1. Thus all numbers are different between downstream and upstream, but names are kept exactly the same. Also add documentation for the rk3576 CRU core. Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com> --- .../bindings/clock/rockchip,rk3576-cru.yaml | 83 +++ .../dt-bindings/clock/rockchip,rk3576-cru.h | 592 ++++++++++++++++++ 2 files changed, 675 insertions(+) create mode 100644 Documentation/devicetree/bindings/clock/rockchip,rk3576-cru.yaml create mode 100644 include/dt-bindings/clock/rockchip,rk3576-cru.h
My bot found errors running 'make dt_binding_check' on your patch: yamllint warnings/errors: dtschema/dtc warnings/errors: Error: Documentation/devicetree/bindings/clock/rockchip,rk3576-cru.example.dts:24.19-20 syntax error FATAL ERROR: Unable to parse input tree make[2]: *** [scripts/Makefile.lib:427: Documentation/devicetree/bindings/clock/rockchip,rk3576-cru.example.dtb] Error 1 make[2]: *** Waiting for unfinished jobs.... make[1]: *** [/builds/robherring/dt-review-ci/linux/Makefile:1430: dt_binding_check] Error 2 make: *** [Makefile:240: __sub-make] Error 2 doc reference errors (make refcheckdocs): See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20240808162258.79271-3-detlev.casanova@collabora.com The base for the series is generally the latest rc1. A different dependency should be noted in *this* patch. If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date: pip3 install dtschema --upgrade Please check and re-submit after running the above command yourself. Note that DT_SCHEMA_FILES can be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.