dt-bindings: arm: mediatek: mediatek,g3dsys: Convert to DT schema
Subsystems (2)
PATCH v3 1/1 dt-bindings: arm: mediatek: mediatek,g3dsys: Convert to DT schema
Convert the MediaTek G3D system controller devicetree binding from the legacy text format to DT schema.
---
Changelog:
Changes since v2:
- Move binding to soc/mediatek directory
- Rename file to mediatek,mt2701-g3dsys.yaml based on fallback compatible
Link to v2:https://lore.kernel.org/all/[email protected]/
Changes since v1:
- Drop redundant description for reg
- Drop redundant description for provider properties
Link to v1:https://lore.kernel.org/all/[email protected]/
--- .../bindings/arm/mediatek/mediatek,g3dsys.txt | 30 ---------- .../soc/mediatek/mediatek,mt2701-g3dsys.yaml | 58 +++++++++++++++++++ 2 files changed, 58 insertions(+), 30 deletions(-) delete mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,g3dsys.txt create mode 100644 Documentation/devicetree/bindings/soc/mediatek/mediatek,mt2701-g3dsys.yaml
Documentation/devicetree/bindings/arm/mediatek/mediatek,g3dsys.txt deleted +0 -30
@@ -1,30 +0,0 @@ -MediaTek g3dsys controller -============================ - -The MediaTek g3dsys controller provides various clocks and reset controller to -the GPU. - -Required Properties: - -- compatible: Should be: - - "mediatek,mt2701-g3dsys", "syscon": - for MT2701 SoC - - "mediatek,mt7623-g3dsys", "mediatek,mt2701-g3dsys", "syscon": - for MT7623 SoC -- #clock-cells: Must be 1 -- #reset-cells: Must be 1 - -The g3dsys controller uses the common clk binding from -Documentation/devicetree/bindings/clock/clock-bindings.txt -The available clocks are defined in dt-bindings/clock/mt*-clk.h. - -Example: - -g3dsys: clock-controller@13000000 { - compatible = "mediatek,mt7623-g3dsys", - "mediatek,mt2701-g3dsys", - "syscon"; - reg = <0 0x13000000 0 0x200>; - #clock-cells = <1>; - #reset-cells = <1>; -};
Documentation/devicetree/bindings/soc/mediatek/mediatek,mt2701-g3dsys.yaml new file +58 -0
58 lines not on this page · raw message
Signature · 1 line
2.34.1
Rob Herring (Arm)
maintainerQuoted 16 lines · Udaya Kiran Challa
Convert the MediaTek G3D system controller devicetree binding from the legacy text format to DT schema.
Signed-off-by Udaya Kiran Challa <[email protected]>---
Changelog:
Changes since v2:
- Move binding to soc/mediatek directory
- Rename file to mediatek,mt2701-g3dsys.yaml based on fallback compatibleLink to v2:https://lore.kernel.org/all/[email protected]/
Changes since v1:
- Drop redundant description for reg
- Drop redundant description for provider properties
Quoted 8 lines
Link to v1:https://lore.kernel.org/all/[email protected]/
--- .../bindings/arm/mediatek/mediatek,g3dsys.txt | 30 ---------- .../soc/mediatek/mediatek,mt2701-g3dsys.yaml | 58 +++++++++++++++++++ 2 files changed, 58 insertions(+), 30 deletions(-) delete mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,g3dsys.txt create mode 100644 Documentation/devicetree/bindings/soc/mediatek/mediatek,mt2701-g3dsys.yaml
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/soc/mediatek/mediatek,mt2701-g3dsys.yaml: $id: Cannot determine base path from $id, relative path/filename doesn't match actual path or filename
$id: http://devicetree.org/schemas/arm/mediatek/mediatek,mt2701-g3dsys.yaml
file: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/soc/mediatek/mediatek,mt2701-g3dsys.yaml
doc reference errors (make refcheckdocs):
See https://patchwork.kernel.org/project/devicetree/patch/[email protected]
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.
Quoted 48 lines · Rob Herring (Arm)
Quoted 16 lines · Udaya Kiran Challa
Convert the MediaTek G3D system controller devicetree binding from the legacy text format to DT schema.
Signed-off-by Udaya Kiran Challa <[email protected]>---
Changelog:
Changes since v2:
- Move binding to soc/mediatek directory
- Rename file to mediatek,mt2701-g3dsys.yaml based on fallback compatibleLink to v2:https://lore.kernel.org/all/[email protected]/
Changes since v1:
- Drop redundant description for reg
- Drop redundant description for provider propertiesQuoted 8 lines
Link to v1:https://lore.kernel.org/all/[email protected]/
--- .../bindings/arm/mediatek/mediatek,g3dsys.txt | 30 ---------- .../soc/mediatek/mediatek,mt2701-g3dsys.yaml | 58 +++++++++++++++++++ 2 files changed, 58 insertions(+), 30 deletions(-) delete mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,g3dsys.txt create mode 100644 Documentation/devicetree/bindings/soc/mediatek/mediatek,mt2701-g3dsys.yamlMy bot found errors running 'make
dt_binding_check' on your patch:yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/soc/mediatek/mediatek,mt2701-g3dsys.yaml: $id: Cannot determine base path from $id, relative path/filename doesn't match actual path or filename
$id: http://devicetree.org/schemas/arm/mediatek/mediatek,mt2701-g3dsys.yaml
file: /builds/robherring/dt-review-ci/linux/Documentation/devicetree/bindings/soc/mediatek/mediatek,mt2701-g3dsys.yamldoc reference errors (make refcheckdocs):
See https://patchwork.kernel.org/project/devicetree/patch/[email protected]
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:
Quoted 6 lines
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note that
DT_SCHEMA_FILEScan be set to your schema file to speed up checking your schema. However, it must be unset to test all examples with your schema.
Apologies Rob, this seems to have been missed in the submitted patch. The dt_binding_check passes successfully on my end. I will send an updated patch shortly.