# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2 --- $id: http://devicetree.org/schemas/pinctrl/mediatek,mt8365-pinctrl.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# title: MediaTek MT8365 Pin Controller maintainers: - Zhiyong Tao - Bernhard Rosenkränzer description: The MediaTek's MT8365 Pin controller is used to control SoC pins. properties: compatible: const: mediatek,mt8365-pinctrl reg: maxItems: 1 mediatek,pctl-regmap: $ref: /schemas/types.yaml#/definitions/phandle-array items: maxItems: 1 minItems: 1 maxItems: 2 description: Should be phandles of the syscfg node. 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 patternProperties: "-pins$": type: object additionalProperties: false patternProperties: "pins$": type: object additionalProperties: false description: A pinctrl node should contain at least one subnode 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: oneOf: - type: boolean - enum: [100, 101, 102, 103] description: Pull up R1/R0 type define value. description: | For pull up type is normal, it don't need add R1/R0 define. For pull up type is R1/R0 type, it can add value to set different resistance. Valid arguments are described as below: 100: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 101: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled. 102: (R1, R0) = (1, 0) which means R1 enabled and R0 disabled. 103: (R1, R0) = (1, 1) which means R1 enabled and R0 enabled. bias-pull-down: oneOf: - type: boolean - enum: [100, 101, 102, 103] description: Pull down R1/R0 type define value. description: | For pull down type is normal, it don't need add R1/R0 define. For pull down type is R1/R0 type, it can add value to set different resistance. Valid arguments are described as below: 100: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 101: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled. 102: (R1, R0) = (1, 0) which means R1 enabled and R0 disabled. 103: (R1, R0) = (1, 1) which means R1 enabled and R0 enabled. drive-strength: enum: [2, 4, 6, 8, 10, 12, 14, 16] input-enable: true input-disable: true output-low: true output-high: true input-schmitt-enable: true input-schmitt-disable: true drive-strength-microamp: enum: [125, 250, 500, 1000] mediatek,drive-strength-adv: deprecated: true description: | DEPRECATED: Please use drive-strength-microamp instead. Describe the specific driving setup property. For I2C pins, the existing generic driving setup can only support 2/4/6/8/10/12/14/16mA driving. But in specific driving setup, they can support 0.125/0.25/0.5/1mA adjustment. If we enable specific driving setup, the existing generic setup will be disabled. The specific driving setup is controlled by E1E0EN. When E1=0/E0=0, the strength is 0.125mA. When E1=0/E0=1, the strength is 0.25mA. When E1=1/E0=0, the strength is 0.5mA. When E1=1/E0=1, the strength is 1mA. EN is used to enable or disable the specific driving setup. Valid arguments are described as below: 0: (E1, E0, EN) = (0, 0, 0) 1: (E1, E0, EN) = (0, 0, 1) 2: (E1, E0, EN) = (0, 1, 0) 3: (E1, E0, EN) = (0, 1, 1) 4: (E1, E0, EN) = (1, 0, 0) 5: (E1, E0, EN) = (1, 0, 1) 6: (E1, E0, EN) = (1, 1, 0) 7: (E1, E0, EN) = (1, 1, 1) So the valid arguments are from 0 to 7. $ref: /schemas/types.yaml#/definitions/uint32 enum: [0, 1, 2, 3, 4, 5, 6, 7] mediatek,pull-up-adv: deprecated: true description: | DEPRECATED: Please use bias-pull-up instead. Pull up 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,pull-down-adv: deprecated: true description: | DEPRECATED: Please use bias-pull-down instead. 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 required: - compatible - reg - gpio-controller - "#gpio-cells" allOf: - $ref: pinctrl.yaml# additionalProperties: false examples: - | #include #include soc { #address-cells = <2>; #size-cells = <2>; pio: pinctrl@1000b000 { compatible = "mediatek,mt8365-pinctrl"; reg = <0 0x1000b000 0 0x1000>; mediatek,pctl-regmap = <&syscfg_pctl>; gpio-controller; #gpio-cells = <2>; interrupt-controller; #interrupt-cells = <2>; interrupts = ; pio-pins { pins { pinmux = , ; mediatek,pull-up-adv = <3>; bias-pull-up; }; }; }; };