# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2 --- $id: http://devicetree.org/schemas/pinctrl/mediatek,mt6797-pinctrl.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# title: Mediatek MT6797 Pin Controller maintainers: - Sean Wang description: |+ The MediaTek's MT6797 Pin controller is used to control SoC pins. properties: compatible: const: mediatek,mt6797-pinctrl reg: minItems: 5 maxItems: 5 reg-names: items: - const: gpio - const: iocfgl - const: iocfgb - const: iocfgr - const: iocfgt gpio-controller: true "#gpio-cells": const: 2 description: | Number of cells in GPIO specifier. Since the generic GPIO binding is used, the amount of cells must be specified as 2. See the below mentioned gpio binding representation for description of particular cells. interrupt-controller: true interrupts: maxItems: 1 "#interrupt-cells": const: 2 allOf: - $ref: "pinctrl.yaml#" required: - compatible - reg - reg-names - gpio-controller - "#gpio-cells" patternProperties: '-[0-9]+$': type: object additionalProperties: false patternProperties: 'pins': type: object additionalProperties: false description: | A pinctrl node should contain at least one subnodes representing the pinctrl groups available on the machine. Each subnode will list the pins it needs, and how they should be configured, with regard to muxer configuration, pullups, drive strength, input enable/disable and input schmitt. $ref: "/schemas/pinctrl/pincfg-node.yaml" properties: pinmux: description: integer array, represents gpio pin number and mux setting. Supported pin number and mux varies for different SoCs, and are defined as macros in -pinfunc.h directly. bias-disable: true bias-pull-up: true bias-pull-down: true input-enable: true input-disable: true output-enable: true output-low: true output-high: true input-schmitt-enable: true input-schmitt-disable: true drive-strength: enum: [2, 4, 8, 12, 16] slew-rate: enum: [0, 1] mediatek,pull-up-adv: description: | Pull up setings for 2 pull resistors, R0 and R1. User can configure those special pins. Valid arguments are described as below: 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled. 2: (R1, R0) = (1, 0) which means R1 enabled and R0 disabled. 3: (R1, R0) = (1, 1) which means R1 enabled and R0 enabled. $ref: /schemas/types.yaml#/definitions/uint32 enum: [0, 1, 2, 3] mediatek,pull-down-adv: description: | Pull down settings for 2 pull resistors, R0 and R1. User can configure those special pins. Valid arguments are described as below: 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled. 2: (R1, R0) = (1, 0) which means R1 enabled and R0 disabled. 3: (R1, R0) = (1, 1) which means R1 enabled and R0 enabled. $ref: /schemas/types.yaml#/definitions/uint32 enum: [0, 1, 2, 3] mediatek,tdsel: description: | An integer describing the steps for output level shifter duty cycle when asserted (high pulse width adjustment). Valid arguments are from 0 to 15. $ref: /schemas/types.yaml#/definitions/uint32 mediatek,rdsel: description: | An integer describing the steps for input level shifter duty cycle when asserted (high pulse width adjustment). Valid arguments are from 0 to 63. $ref: /schemas/types.yaml#/definitions/uint32 required: - pinmux additionalProperties: false examples: - | #include #include #include soc { #address-cells = <2>; #size-cells = <2>; pio: pinctrl@10005000 { compatible = "mediatek,mt6797-pinctrl"; reg = <0 0x10005000 0 0x1000>, <0 0x10002000 0 0x400>, <0 0x10002400 0 0x400>, <0 0x10002800 0 0x400>, <0 0x10002C00 0 0x400>; reg-names = "gpio", "iocfgl", "iocfgb", "iocfgr", "iocfgt"; gpio-controller; #gpio-cells = <2>; uart_pins_a: uart-0 { pins1 { pinmux = , ; }; }; }; };