Re: [PATCH 02/15] dt-bindings: clock: mediatek: regroup MT8188 dt-bindings into MT8186
From: "Rob Herring (Arm)" <robh@kernel.org>
Date: 2026-07-01 16:24:34
Also in:
linux-clk, linux-devicetree, linux-mediatek, lkml, netdev
On Wed, 01 Jul 2026 15:11:07 +0200, Louis-Alexis Eyraud wrote:
Regroup the MT8188 clock and system clock dt-bindings into MT8186 ones to ease maintainability and have common files for several currently supported SoC or new future ones, that have the same kind of clock controller design. Note: The `#clock-cells` property is a required property for all compatibles declared in MT8188 clock and system clock dt-bindings but not in MT8186 ones. To avoid ABI breakage, conditional blocks to check this requirement for MT8188 compatibles are added, rather than enforcing it for MT8186 compatibles. Signed-off-by: Louis-Alexis Eyraud <redacted> --- .../bindings/clock/mediatek,mt8186-clock.yaml | 82 ++++++++++++++++++- .../bindings/clock/mediatek,mt8186-sys-clock.yaml | 20 ++++- .../bindings/clock/mediatek,mt8188-clock.yaml | 93 ---------------------- .../bindings/clock/mediatek,mt8188-sys-clock.yaml | 58 -------------- 4 files changed, 100 insertions(+), 153 deletions(-)
My bot found errors running 'make dt_binding_check' on your patch: yamllint warnings/errors: ./Documentation/devicetree/bindings/clock/mediatek,mt8186-clock.yaml:62:1: [warning] too many blank lines (2 > 1) (empty-lines) dtschema/dtc warnings/errors: doc reference errors (make refcheckdocs): See https://patchwork.kernel.org/project/devicetree/patch/20260701-mt8189-clocks-system-base-v1-2-2b048feea50a@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.