.../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
Convert the MediaTek G3D system controller devicetree binding
from the legacy text format to DT schema.
Signed-off-by: Udaya Kiran Challa <challauday369@gmail.com>
---
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/20260323180616.23333-1-challauday369@gmail.com/
Changes since v1:
- Drop redundant description for reg
- Drop redundant description for provider properties
Link to v1:https://lore.kernel.org/all/20260315080302.454233-1-challauday369@gmail.com/
---
.../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
diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,g3dsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,g3dsys.txt
deleted file mode 100644
index 7de43bf41fdc..000000000000
--- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,g3dsys.txt
+++ /dev/null
@@ -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>;
-};
diff --git a/Documentation/devicetree/bindings/soc/mediatek/mediatek,mt2701-g3dsys.yaml b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mt2701-g3dsys.yaml
new file mode 100644
index 000000000000..adfbf1ffb416
--- /dev/null
+++ b/Documentation/devicetree/bindings/soc/mediatek/mediatek,mt2701-g3dsys.yaml
@@ -0,0 +1,58 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/arm/mediatek/mediatek,mt2701-g3dsys.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: MediaTek G3D System Controller
+
+maintainers:
+ - Sean Wang <sean.wang@mediatek.com>
+ - Ryder Lee <ryder.lee@mediatek.com>
+
+description: |
+ The MediaTek G3D system controller provides clocks and reset control
+ for the GPU subsystem on MediaTek SoCs.
+
+properties:
+ compatible:
+ oneOf:
+ - items:
+ - const: mediatek,mt2701-g3dsys
+ - const: syscon
+ - items:
+ - const: mediatek,mt7623-g3dsys
+ - const: mediatek,mt2701-g3dsys
+ - const: syscon
+
+ reg:
+ maxItems: 1
+
+ "#clock-cells":
+ const: 1
+
+ "#reset-cells":
+ const: 1
+
+required:
+ - compatible
+ - reg
+ - "#clock-cells"
+ - "#reset-cells"
+
+additionalProperties: false
+
+examples:
+ - |
+ soc {
+ #address-cells = <2>;
+ #size-cells = <2>;
+ g3dsys: syscon@13000000 {
+ compatible = "mediatek,mt7623-g3dsys",
+ "mediatek,mt2701-g3dsys",
+ "syscon";
+ reg = <0 0x13000000 0 0x200>;
+ #clock-cells = <1>;
+ #reset-cells = <1>;
+ };
+ };
--
2.34.1On Wed, 25 Mar 2026 23:45:09 +0530, Udaya Kiran Challa wrote: > Convert the MediaTek G3D system controller devicetree binding > from the legacy text format to DT schema. > > Signed-off-by: Udaya Kiran Challa <challauday369@gmail.com> > --- > 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/20260323180616.23333-1-challauday369@gmail.com/ > > Changes since v1: > - Drop redundant description for reg > - Drop redundant description for provider properties > > Link to v1:https://lore.kernel.org/all/20260315080302.454233-1-challauday369@gmail.com/ > --- > .../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/20260325181509.3430-1-challauday369@gmail.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.
On Thu, Mar 26, 2026 at 5:01 AM Rob Herring (Arm) <robh@kernel.org> wrote: > > > On Wed, 25 Mar 2026 23:45:09 +0530, Udaya Kiran Challa wrote: > > Convert the MediaTek G3D system controller devicetree binding > > from the legacy text format to DT schema. > > > > Signed-off-by: Udaya Kiran Challa <challauday369@gmail.com> > > --- > > 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/20260323180616.23333-1-challauday369@gmail.com/ > > > > Changes since v1: > > - Drop redundant description for reg > > - Drop redundant description for provider properties > > > > Link to v1:https://lore.kernel.org/all/20260315080302.454233-1-challauday369@gmail.com/ > > --- > > .../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/20260325181509.3430-1-challauday369@gmail.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. > 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.
© 2016 - 2026 Red Hat, Inc.