Re: [PATCH v1 1/2] dt-bindings: clock: mediatek: Describe MT6789 clock controllers

["Rob Herring (Arm)" <robh@kernel.org>]

On Wed, 16 Jul 2025 02:22:20 +0400, Arseniy Velikanov wrote:
> Add new bindings for system clocks and functional clocks on
> MediaTek MT6789.
> 
> Signed-off-by: Arseniy Velikanov <me@adomerle.pw>
> ---
>  .../bindings/clock/mediatek,mt6789-clock.yaml | 142 +++++++
>  .../clock/mediatek,mt6789-sys-clock.yaml      |  68 +++
>  .../dt-bindings/clock/mediatek,mt6789-clk.h   | 390 ++++++++++++++++++
>  .../reset/mediatek,mt6789-resets.h            |  15 +
>  4 files changed, 615 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/clock/mediatek,mt6789-clock.yaml
>  create mode 100644 Documentation/devicetree/bindings/clock/mediatek,mt6789-sys-clock.yaml
>  create mode 100644 include/dt-bindings/clock/mediatek,mt6789-clk.h
>  create mode 100644 include/dt-bindings/reset/mediatek,mt6789-resets.h
> 

My bot found errors running 'make dt_binding_check' on your patch:

yamllint warnings/errors:

dtschema/dtc warnings/errors:
Documentation/devicetree/bindings/clock/mediatek,mt6789-sys-clock.example.dtb: /example-2/syscon@10001000: failed to match any schema with compatible: ['mt6789-infracfg-ao', 'syscon']
Documentation/devicetree/bindings/clock/mediatek,mt6789-clock.example.dtb: /example-4/clock-controller@11f01000: failed to match any schema with compatible: ['mediatek,mt6789-imp-iic-wrap-n']

doc reference errors (make refcheckdocs):

See https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20250715222221.29406-1-me@adomerle.pw

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.