Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

dt-bindings: pinctrl: {mediatek,ralink}: fix formatting

Change the style of description properties to plain style where there's no
need to preserve the line endings, and vice versa.

Fix capitalisation and indentation.

Fit the schemas to 80 columns for each line.

Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20230317213011.13656-16-arinc.unal@arinc9.com
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

authored by

Arınç ÜNAL and committed by
Linus Walleij
c911ad22 a9d44c4c

+258 -238
+11 -11
Documentation/devicetree/bindings/pinctrl/mediatek,mt65xx-pinctrl.yaml
··· 9 9 maintainers: 10 10 - Sean Wang <sean.wang@kernel.org> 11 11 12 - description: |+ 12 + description: 13 13 The MediaTek's MT65xx Pin controller is used to control SoC pins. 14 14 15 15 properties: ··· 30 30 31 31 pins-are-numbered: 32 32 $ref: /schemas/types.yaml#/definitions/flag 33 - description: | 33 + description: 34 34 Specify the subnodes are using numbered pinmux to specify pins. (UNUSED) 35 35 deprecated: true 36 36 ··· 38 38 39 39 "#gpio-cells": 40 40 const: 2 41 - description: | 42 - Number of cells in GPIO specifier. Since the generic GPIO 43 - binding is used, the amount of cells must be specified as 2. See the below 44 - mentioned gpio binding representation for description of particular cells. 41 + description: 42 + Number of cells in GPIO specifier. Since the generic GPIO binding is used, 43 + the amount of cells must be specified as 2. See the below mentioned gpio 44 + binding representation for description of particular cells. 45 45 46 46 mediatek,pctl-regmap: 47 47 $ref: /schemas/types.yaml#/definitions/phandle-array ··· 49 49 maxItems: 1 50 50 minItems: 1 51 51 maxItems: 2 52 - description: | 52 + description: 53 53 Should be phandles of the syscfg node. 54 54 55 55 interrupt-controller: true ··· 77 77 '(^pins|pins?$)': 78 78 type: object 79 79 additionalProperties: false 80 - description: | 80 + description: 81 81 A pinctrl node should contain at least one subnodes representing the 82 82 pinctrl groups available on the machine. Each subnode will list the 83 83 pins it needs, and how they should be configured, with regard to muxer ··· 88 88 properties: 89 89 pinmux: 90 90 description: 91 - integer array, represents gpio pin number and mux setting. 91 + Integer array, represents gpio pin number and mux setting. 92 92 Supported pin number and mux varies for different SoCs, and are 93 93 defined as macros in <soc>-pinfunc.h directly. 94 94 95 95 bias-disable: true 96 96 97 97 bias-pull-up: 98 - description: | 98 + description: 99 99 Besides generic pinconfig options, it can be used as the pull up 100 100 settings for 2 pull resistors, R0 and R1. User can configure those 101 101 special pins. Some macros have been defined for this usage, such ··· 117 117 input-schmitt-disable: true 118 118 119 119 drive-strength: 120 - description: | 120 + description: 121 121 Can support some arguments, such as MTK_DRIVE_4mA, MTK_DRIVE_6mA, 122 122 etc. See dt-bindings/pinctrl/mt65xx.h for valid arguments. 123 123
+18 -15
Documentation/devicetree/bindings/pinctrl/mediatek,mt6779-pinctrl.yaml
··· 11 11 - Sean Wang <sean.wang@kernel.org> 12 12 13 13 description: 14 - The MediaTek pin controller on MT6779 is used to control pin 15 - functions, pull up/down resistance and drive strength options. 14 + The MediaTek pin controller on MT6779 is used to control pin functions, pull 15 + up/down resistance and drive strength options. 16 16 17 17 properties: 18 18 compatible: ··· 29 29 30 30 "#gpio-cells": 31 31 const: 2 32 - description: | 33 - Number of cells in GPIO specifier. Since the generic GPIO 34 - binding is used, the amount of cells must be specified as 2. See the below 35 - mentioned gpio binding representation for description of particular cells. 32 + description: 33 + Number of cells in GPIO specifier. Since the generic GPIO binding is used, 34 + the amount of cells must be specified as 2. See the below mentioned gpio 35 + binding representation for description of particular cells. 36 36 37 37 gpio-ranges: 38 38 minItems: 1 39 39 maxItems: 5 40 - description: | 40 + description: 41 41 GPIO valid number range. 42 42 43 43 interrupt-controller: true 44 44 45 45 interrupts: 46 46 maxItems: 1 47 - description: | 47 + description: 48 48 Specifies the summary IRQ. 49 49 50 50 "#interrupt-cells": ··· 118 118 patternProperties: 119 119 '-pins*$': 120 120 type: object 121 - description: | 121 + description: 122 122 A pinctrl node should contain at least one subnodes representing the 123 123 pinctrl groups available on the machine. Each subnode will list the 124 124 pins it needs, and how they should be configured, with regard to muxer 125 - configuration, pullups, drive strength, input enable/disable and input schmitt. 125 + configuration, pullups, drive strength, input enable/disable and input 126 + schmitt. 126 127 $ref: "/schemas/pinctrl/pincfg-node.yaml" 127 128 128 129 properties: 129 130 pinmux: 130 131 description: 131 - integer array, represents gpio pin number and mux setting. 132 - Supported pin number and mux varies for different SoCs, and are defined 133 - as macros in boot/dts/<soc>-pinfunc.h directly. 132 + Integer array, represents gpio pin number and mux setting. 133 + Supported pin number and mux varies for different SoCs, and are 134 + defined as macros in boot/dts/<soc>-pinfunc.h directly. 134 135 135 136 bias-disable: true 136 137 ··· 160 159 mediatek,pull-up-adv: 161 160 description: | 162 161 Pull up setings for 2 pull resistors, R0 and R1. User can 163 - configure those special pins. Valid arguments are described as below: 162 + configure those special pins. Valid arguments are described as 163 + below: 164 164 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 165 165 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled. 166 166 2: (R1, R0) = (1, 0) which means R1 enabled and R0 disabled. ··· 172 170 mediatek,pull-down-adv: 173 171 description: | 174 172 Pull down settings for 2 pull resistors, R0 and R1. User can 175 - configure those special pins. Valid arguments are described as below: 173 + configure those special pins. Valid arguments are described as 174 + below: 176 175 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 177 176 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled. 178 177 2: (R1, R0) = (1, 0) which means R1 enabled and R0 disabled.
+21 -20
Documentation/devicetree/bindings/pinctrl/mediatek,mt6795-pinctrl.yaml
··· 10 10 - AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com> 11 11 - Sean Wang <sean.wang@kernel.org> 12 12 13 - description: | 13 + description: 14 14 The MediaTek's MT6795 Pin controller is used to control SoC pins. 15 15 16 16 properties: ··· 20 20 gpio-controller: true 21 21 22 22 '#gpio-cells': 23 - description: | 23 + description: 24 24 Number of cells in GPIO specifier. Since the generic GPIO binding is used, 25 - the amount of cells must be specified as 2. See the below 26 - mentioned gpio binding representation for description of particular cells. 25 + the amount of cells must be specified as 2. See the below mentioned gpio 26 + binding representation for description of particular cells. 27 27 const: 2 28 28 29 29 gpio-ranges: ··· 32 32 33 33 reg: 34 34 description: 35 - Physical address base for gpio base and eint registers. 35 + Physical address base for GPIO base and eint registers. 36 36 minItems: 2 37 37 38 38 reg-names: ··· 65 65 A pinctrl node should contain at least one subnodes representing the 66 66 pinctrl groups available on the machine. Each subnode will list the 67 67 pins it needs, and how they should be configured, with regard to muxer 68 - configuration, pullups, drive strength, input enable/disable and 69 - input schmitt. 68 + configuration, pullups, drive strength, input enable/disable and input 69 + schmitt. 70 70 An example of using macro: 71 71 pincontroller { 72 72 /* GPIO0 set as multifunction GPIO0 */ ··· 86 86 87 87 properties: 88 88 pinmux: 89 - description: | 89 + description: 90 90 Integer array, represents gpio pin number and mux setting. 91 91 Supported pin number and mux varies for different SoCs, and are 92 - defined as macros in dt-bindings/pinctrl/<soc>-pinfunc.h 93 - directly. 92 + defined as macros in dt-bindings/pinctrl/<soc>-pinfunc.h directly. 94 93 95 94 drive-strength: 96 95 enum: [2, 4, 6, 8, 10, 12, 14, 16] ··· 99 100 - type: boolean 100 101 - enum: [100, 101, 102, 103] 101 102 description: mt6795 pull down PUPD/R0/R1 type define value. 102 - description: | 103 - For normal pull down type, it is not necessary to specify R1R0 104 - values; When pull down type is PUPD/R0/R1, adding R1R0 defines 105 - will set different resistance values. 103 + description: 104 + For normal pull down type, it is not necessary to specify R1R0 105 + values; When pull down type is PUPD/R0/R1, adding R1R0 defines 106 + will set different resistance values. 106 107 107 108 bias-pull-up: 108 109 oneOf: 109 110 - type: boolean 110 111 - enum: [100, 101, 102, 103] 111 112 description: mt6795 pull up PUPD/R0/R1 type define value. 112 - description: | 113 - For normal pull up type, it is not necessary to specify R1R0 114 - values; When pull up type is PUPD/R0/R1, adding R1R0 defines 115 - will set different resistance values. 113 + description: 114 + For normal pull up type, it is not necessary to specify R1R0 115 + values; When pull up type is PUPD/R0/R1, adding R1R0 defines will 116 + set different resistance values. 116 117 117 118 bias-disable: true 118 119 ··· 131 132 mediatek,pull-up-adv: 132 133 description: | 133 134 Pull up setings for 2 pull resistors, R0 and R1. User can 134 - configure those special pins. Valid arguments are described as below: 135 + configure those special pins. Valid arguments are described as 136 + below: 135 137 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 136 138 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled. 137 139 2: (R1, R0) = (1, 0) which means R1 enabled and R0 disabled. ··· 143 143 mediatek,pull-down-adv: 144 144 description: | 145 145 Pull down settings for 2 pull resistors, R0 and R1. User can 146 - configure those special pins. Valid arguments are described as below: 146 + configure those special pins. Valid arguments are described as 147 + below: 147 148 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 148 149 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled. 149 150 2: (R1, R0) = (1, 0) which means R1 enabled and R0 disabled.
+1 -1
Documentation/devicetree/bindings/pinctrl/mediatek,mt7620-pinctrl.yaml
··· 10 10 - Arınç ÜNAL <arinc.unal@arinc9.com> 11 11 - Sergio Paracuellos <sergio.paracuellos@gmail.com> 12 12 13 - description: 13 + description: | 14 14 MediaTek MT7620 pin controller for MT7620, MT7628 and MT7688 SoCs. 15 15 The pin controller can only set the muxing of pin groups. Muxing individual 16 16 pins is not supported. There is no pinconf support.
+1 -1
Documentation/devicetree/bindings/pinctrl/mediatek,mt7621-pinctrl.yaml
··· 10 10 - Arınç ÜNAL <arinc.unal@arinc9.com> 11 11 - Sergio Paracuellos <sergio.paracuellos@gmail.com> 12 12 13 - description: 13 + description: | 14 14 MediaTek MT7621 pin controller for MT7621 SoC. 15 15 The pin controller can only set the muxing of pin groups. Muxing individual 16 16 pins is not supported. There is no pinconf support.
+13 -13
Documentation/devicetree/bindings/pinctrl/mediatek,mt7622-pinctrl.yaml
··· 9 9 maintainers: 10 10 - Sean Wang <sean.wang@kernel.org> 11 11 12 - description: |+ 12 + description: 13 13 The MediaTek's MT7622 Pin controller is used to control SoC pins. 14 14 15 15 properties: ··· 29 29 30 30 "#gpio-cells": 31 31 const: 2 32 - description: | 33 - Number of cells in GPIO specifier. Since the generic GPIO 34 - binding is used, the amount of cells must be specified as 2. See the below 35 - mentioned gpio binding representation for description of particular cells. 32 + description: 33 + Number of cells in GPIO specifier. Since the generic GPIO binding is used, 34 + the amount of cells must be specified as 2. See the below mentioned gpio 35 + binding representation for description of particular cells. 36 36 37 37 interrupt-controller: true 38 38 ··· 68 68 '^mux(-|$)': 69 69 type: object 70 70 additionalProperties: false 71 - description: | 71 + description: 72 72 pinmux configuration nodes. 73 73 $ref: "/schemas/pinctrl/pinmux-node.yaml" 74 74 properties: 75 75 function: 76 - description: | 76 + description: 77 77 A string containing the name of the function to mux to the group. 78 78 enum: [emmc, eth, i2c, i2s, ir, led, flash, pcie, pmic, pwm, sd, 79 79 spi, tdm, uart, watchdog, wifi] 80 80 81 81 groups: 82 - description: | 82 + description: 83 83 An array of strings. Each string contains the name of a group. 84 84 85 85 drive-strength: ··· 247 247 '^conf(-|$)': 248 248 type: object 249 249 additionalProperties: false 250 - description: | 250 + description: 251 251 pinconf configuration nodes. 252 252 $ref: "/schemas/pinctrl/pincfg-node.yaml" 253 253 254 254 properties: 255 255 groups: 256 - description: | 256 + description: 257 257 An array of strings. Each string contains the name of a group. 258 258 Valid values are the same as the pinmux node. 259 259 260 260 pins: 261 - description: | 261 + description: 262 262 An array of strings. Each string contains the name of a pin. 263 263 enum: [GPIO_A, I2S1_IN, I2S1_OUT, I2S_BCLK, I2S_WS, I2S_MCLK, TXD0, 264 264 RXD0, SPI_WP, SPI_HOLD, SPI_CLK, SPI_MOSI, SPI_MISO, SPI_CS, ··· 315 315 enum: [0, 1] 316 316 317 317 mediatek,tdsel: 318 - description: | 318 + description: 319 319 An integer describing the steps for output level shifter duty 320 320 cycle when asserted (high pulse width adjustment). Valid arguments 321 321 are from 0 to 15. 322 322 $ref: /schemas/types.yaml#/definitions/uint32 323 323 324 324 mediatek,rdsel: 325 - description: | 325 + description: 326 326 An integer describing the steps for input level shifter duty cycle 327 327 when asserted (high pulse width adjustment). Valid arguments are 328 328 from 0 to 63.
+19 -14
Documentation/devicetree/bindings/pinctrl/mediatek,mt7981-pinctrl.yaml
··· 37 37 38 38 "#gpio-cells": 39 39 const: 2 40 - description: > 40 + description: 41 41 Number of cells in GPIO specifier. Since the generic GPIO binding is used, 42 42 the amount of cells must be specified as 2. See the below mentioned gpio 43 43 binding representation for description of particular cells. ··· 111 111 "watchdog1" "watchdog" 13 112 112 "udi" "udi" 9, 10, 11, 12, 13 113 113 "drv_vbus" "usb" 14 114 - "emmc_45" "flash" 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25 114 + "emmc_45" "flash" 15, 16, 17, 18, 19, 20, 21, 22, 23, 115 + 24, 25 116 + 115 117 "snfi" "flash" 16, 17, 18, 19, 20, 21 116 118 "spi0" "spi" 16, 17, 18, 19 117 119 "spi0_wp_hold" "spi" 20, 21 ··· 150 148 "wf5g_led0" "led" 31 151 149 "wf5g_led1" "led" 35 152 150 "mt7531_int" "eth" 38 153 - "ant_sel" "ant" 14, 15, 16, 17, 18, 19, 20, 21, 22 151 + "ant_sel" "ant" 14, 15, 16, 17, 18, 19, 20, 21, 22, 154 152 23, 24, 25, 34, 35 155 153 156 154 $ref: /schemas/pinctrl/pinmux-node.yaml ··· 258 256 then: 259 257 properties: 260 258 groups: 261 - enum: [gbe_led0, gbe_led1, wf2g_led0, wf2g_led1, wf5g_led0, wf5g_led1] 259 + enum: [gbe_led0, gbe_led1, wf2g_led0, wf2g_led1, wf5g_led0, 260 + wf5g_led1] 262 261 - if: 263 262 properties: 264 263 function: ··· 278 275 properties: 279 276 groups: 280 277 items: 281 - enum: [spi1_0, spi0, spi0_wp_hold, spi1_1, spi2, spi2_wp_hold] 278 + enum: [spi1_0, spi0, spi0_wp_hold, spi1_1, spi2, 279 + spi2_wp_hold] 282 280 maxItems: 4 283 281 - if: 284 282 properties: ··· 336 332 JTAG_JTDO, JTAG_JTDI, JTAG_JTMS, JTAG_JTCLK, JTAG_JTRST_N, 337 333 WO_JTAG_JTDO, WO_JTAG_JTDI, WO_JTAG_JTMS, WO_JTAG_JTCLK, 338 334 WO_JTAG_JTRST_N, USB_VBUS, PWM0, SPI0_CLK, SPI0_MOSI, 339 - SPI0_MISO, SPI0_CS, SPI0_HOLD, SPI0_WP, SPI1_CLK, SPI1_MOSI, 340 - SPI1_MISO, SPI1_CS, SPI2_CLK, SPI2_MOSI, SPI2_MISO, SPI2_CS, 341 - SPI2_HOLD, SPI2_WP, UART0_RXD, UART0_TXD, PCIE_CLK_REQ, 342 - PCIE_WAKE_N, SMI_MDC, SMI_MDIO, GBE_INT, GBE_RESET, 343 - WF_DIG_RESETB, WF_CBA_RESETB, WF_XO_REQ, WF_TOP_CLK, 344 - WF_TOP_DATA, WF_HB1, WF_HB2, WF_HB3, WF_HB4, WF_HB0, 345 - WF_HB0_B, WF_HB5, WF_HB6, WF_HB7, WF_HB8, WF_HB9, WF_HB10] 335 + SPI0_MISO, SPI0_CS, SPI0_HOLD, SPI0_WP, SPI1_CLK, 336 + SPI1_MOSI, SPI1_MISO, SPI1_CS, SPI2_CLK, SPI2_MOSI, 337 + SPI2_MISO, SPI2_CS, SPI2_HOLD, SPI2_WP, UART0_RXD, 338 + UART0_TXD, PCIE_CLK_REQ, PCIE_WAKE_N, SMI_MDC, SMI_MDIO, 339 + GBE_INT, GBE_RESET, WF_DIG_RESETB, WF_CBA_RESETB, 340 + WF_XO_REQ, WF_TOP_CLK, WF_TOP_DATA, WF_HB1, WF_HB2, WF_HB3, 341 + WF_HB4, WF_HB0, WF_HB0_B, WF_HB5, WF_HB6, WF_HB7, WF_HB8, 342 + WF_HB9, WF_HB10] 346 343 maxItems: 57 347 344 348 345 bias-disable: true ··· 353 348 - type: boolean 354 349 description: normal pull up. 355 350 - enum: [100, 101, 102, 103] 356 - description: > 351 + description: 357 352 PUPD/R1/R0 pull down type. See MTK_PUPD_SET_R1R0 defines in 358 353 dt-bindings/pinctrl/mt65xx.h. 359 354 ··· 362 357 - type: boolean 363 358 description: normal pull down. 364 359 - enum: [100, 101, 102, 103] 365 - description: > 360 + description: 366 361 PUPD/R1/R0 pull down type. See MTK_PUPD_SET_R1R0 defines in 367 362 dt-bindings/pinctrl/mt65xx.h. 368 363
+35 -33
Documentation/devicetree/bindings/pinctrl/mediatek,mt7986-pinctrl.yaml
··· 9 9 maintainers: 10 10 - Sean Wang <sean.wang@kernel.org> 11 11 12 - description: |+ 12 + description: 13 13 The MediaTek's MT7986 Pin controller is used to control SoC pins. 14 14 15 15 properties: ··· 37 37 38 38 "#gpio-cells": 39 39 const: 2 40 - description: | 41 - Number of cells in GPIO specifier. Since the generic GPIO 42 - binding is used, the amount of cells must be specified as 2. See the below 43 - mentioned gpio binding representation for description of particular cells. 40 + description: 41 + Number of cells in GPIO specifier. Since the generic GPIO binding is used, 42 + the amount of cells must be specified as 2. See the below mentioned gpio 43 + binding representation for description of particular cells. 44 44 45 45 gpio-ranges: 46 46 minItems: 1 47 47 maxItems: 5 48 - description: | 48 + description: 49 49 GPIO valid number range. 50 50 51 51 interrupt-controller: true ··· 81 81 The following table shows the effective values of "group", "function" 82 82 properties and chip pinout pins 83 83 84 - groups function pins (in pin#) 84 + groups function pins (in pin#) 85 85 --------------------------------------------------------------------- 86 86 "watchdog" "watchdog" 0 87 87 "wifi_led" "led" 1, 2 ··· 97 97 "pwm1_0" "pwm" 22, 98 98 "snfi" "flash" 23, 24, 25, 26, 27, 28 99 99 "spi1_2" "spi" 29, 30, 31, 32 100 - "emmc_45" "emmc" 22, 23, 24, 25, 26, 27, 28, 29, 30, 101 - 31, 32 100 + "emmc_45" "emmc" 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 101 + 32 102 + 102 103 "spi1_1" "spi" 23, 24, 25, 26 103 104 "uart1_2_rx_tx" "uart" 29, 30 104 105 "uart1_2_cts_rts" "uart" 31, 32 ··· 116 115 "pcie_pereset" "pcie" 41 117 116 "uart1" "uart" 42, 43, 44, 45 118 117 "uart2" "uart" 46, 47, 48, 49 119 - "emmc_51" "emmc" 50, 51, 52, 53, 54, 55, 56, 57, 57, 120 - 59, 60, 61 118 + "emmc_51" "emmc" 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 119 + 60, 61 120 + 121 121 "pcm" "audio" 62, 63, 64, 65 122 122 "i2s" "audio" 62, 63, 64, 65 123 123 "switch_int" "eth" 66 ··· 131 129 $ref: "/schemas/pinctrl/pinmux-node.yaml" 132 130 properties: 133 131 function: 134 - description: | 132 + description: 135 133 A string containing the name of the function to mux to the group. 136 134 There is no "audio", "pcie" functions on mt7986b, you can only use 137 135 those functions on mt7986a. 138 136 enum: [audio, emmc, eth, i2c, led, flash, pcie, pwm, spi, uart, 139 137 watchdog, wifi] 140 138 groups: 141 - description: | 139 + description: 142 140 An array of strings. Each string contains the name of a group. 143 - There is no "pcie_pereset", "uart1", "uart2" "emmc_51", "pcm", 144 - and "i2s" groups on mt7986b, you can only use those groups on 145 - mt7986a. 141 + There is no "pcie_pereset", "uart1", "uart2" "emmc_51", "pcm", and 142 + "i2s" groups on mt7986b, you can only use those groups on mt7986a. 146 143 required: 147 144 - function 148 145 - groups ··· 259 258 '.*conf.*': 260 259 type: object 261 260 additionalProperties: false 262 - description: | 261 + description: 263 262 pinconf configuration nodes. 264 263 $ref: "/schemas/pinctrl/pincfg-node.yaml" 265 264 266 265 properties: 267 266 pins: 268 - description: | 269 - An array of strings. Each string contains the name of a pin. 270 - There is no PIN 41 to PIN 65 above on mt7686b, you can only use 271 - those pins on mt7986a. 267 + description: 268 + An array of strings. Each string contains the name of a pin. There 269 + is no PIN 41 to PIN 65 above on mt7686b, you can only use those 270 + pins on mt7986a. 272 271 items: 273 272 enum: [SYS_WATCHDOG, WF2G_LED, WF5G_LED, I2C_SCL, I2C_SDA, GPIO_0, 274 273 GPIO_1, GPIO_2, GPIO_3, GPIO_4, GPIO_5, GPIO_6, GPIO_7, 275 - GPIO_8, GPIO_9, GPIO_10, GPIO_11, GPIO_12, GPIO_13, GPIO_14, 276 - GPIO_15, PWM0, PWM1, SPI0_CLK, SPI0_MOSI, SPI0_MISO, SPI0_CS, 277 - SPI0_HOLD, SPI0_WP, SPI1_CLK, SPI1_MOSI, SPI1_MISO, SPI1_CS, 278 - SPI2_CLK, SPI2_MOSI, SPI2_MISO, SPI2_CS, SPI2_HOLD, SPI2_WP, 279 - UART0_RXD, UART0_TXD, PCIE_PERESET_N, UART1_RXD, UART1_TXD, 280 - UART1_CTS, UART1_RTS, UART2_RXD, UART2_TXD, UART2_CTS, 281 - UART2_RTS, EMMC_DATA_0, EMMC_DATA_1, EMMC_DATA_2, 282 - EMMC_DATA_3, EMMC_DATA_4, EMMC_DATA_5, EMMC_DATA_6, 283 - EMMC_DATA_7, EMMC_CMD, EMMC_CK, EMMC_DSL, EMMC_RSTB, PCM_DTX, 284 - PCM_DRX, PCM_CLK, PCM_FS, MT7531_INT, SMI_MDC, SMI_MDIO, 274 + GPIO_8, GPIO_9, GPIO_10, GPIO_11, GPIO_12, GPIO_13, 275 + GPIO_14, GPIO_15, PWM0, PWM1, SPI0_CLK, SPI0_MOSI, 276 + SPI0_MISO, SPI0_CS, SPI0_HOLD, SPI0_WP, SPI1_CLK, 277 + SPI1_MOSI, SPI1_MISO, SPI1_CS, SPI2_CLK, SPI2_MOSI, 278 + SPI2_MISO, SPI2_CS, SPI2_HOLD, SPI2_WP, UART0_RXD, 279 + UART0_TXD, PCIE_PERESET_N, UART1_RXD, UART1_TXD, UART1_CTS, 280 + UART1_RTS, UART2_RXD, UART2_TXD, UART2_CTS, UART2_RTS, 281 + EMMC_DATA_0, EMMC_DATA_1, EMMC_DATA_2, EMMC_DATA_3, 282 + EMMC_DATA_4, EMMC_DATA_5, EMMC_DATA_6, EMMC_DATA_7, 283 + EMMC_CMD, EMMC_CK, EMMC_DSL, EMMC_RSTB, PCM_DTX, PCM_DRX, 284 + PCM_CLK, PCM_FS, MT7531_INT, SMI_MDC, SMI_MDIO, 285 285 WF0_DIG_RESETB, WF0_CBA_RESETB, WF0_XO_REQ, WF0_TOP_CLK, 286 286 WF0_TOP_DATA, WF0_HB1, WF0_HB2, WF0_HB3, WF0_HB4, WF0_HB0, 287 287 WF0_HB0_B, WF0_HB5, WF0_HB6, WF0_HB7, WF0_HB8, WF0_HB9, ··· 299 297 - type: boolean 300 298 description: normal pull up. 301 299 - enum: [100, 101, 102, 103] 302 - description: | 300 + description: 303 301 PUPD/R1/R0 pull down type. See MTK_PUPD_SET_R1R0 defines in 304 302 dt-bindings/pinctrl/mt65xx.h. 305 303 ··· 308 306 - type: boolean 309 307 description: normal pull down. 310 308 - enum: [100, 101, 102, 103] 311 - description: | 309 + description: 312 310 PUPD/R1/R0 pull down type. See MTK_PUPD_SET_R1R0 defines in 313 311 dt-bindings/pinctrl/mt65xx.h. 314 312
+14 -12
Documentation/devicetree/bindings/pinctrl/mediatek,mt8183-pinctrl.yaml
··· 9 9 maintainers: 10 10 - Sean Wang <sean.wang@kernel.org> 11 11 12 - description: |+ 12 + description: 13 13 The MediaTek's MT8183 Pin controller is used to control SoC pins. 14 14 15 15 properties: ··· 37 37 38 38 "#gpio-cells": 39 39 const: 2 40 - description: | 41 - Number of cells in GPIO specifier. Since the generic GPIO 42 - binding is used, the amount of cells must be specified as 2. See the below 43 - mentioned gpio binding representation for description of particular cells. 40 + description: 41 + Number of cells in GPIO specifier. Since the generic GPIO binding is used, 42 + the amount of cells must be specified as 2. See the below mentioned gpio 43 + binding representation for description of particular cells. 44 44 45 45 gpio-ranges: 46 46 minItems: 1 47 47 maxItems: 5 48 - description: | 48 + description: 49 49 GPIO valid number range. 50 50 51 51 interrupt-controller: true ··· 74 74 '^pins': 75 75 type: object 76 76 additionalProperties: false 77 - description: | 77 + description: 78 78 A pinctrl node should contain at least one subnodes representing the 79 79 pinctrl groups available on the machine. Each subnode will list the 80 80 pins it needs, and how they should be configured, with regard to muxer ··· 85 85 properties: 86 86 pinmux: 87 87 description: 88 - integer array, represents gpio pin number and mux setting. 88 + Integer array, represents gpio pin number and mux setting. 89 89 Supported pin number and mux varies for different SoCs, and are 90 90 defined as macros in <soc>-pinfunc.h directly. 91 91 ··· 139 139 mediatek,pull-up-adv: 140 140 description: | 141 141 Pull up setings for 2 pull resistors, R0 and R1. User can 142 - configure those special pins. Valid arguments are described as below: 142 + configure those special pins. Valid arguments are described as 143 + below: 143 144 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 144 145 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled. 145 146 2: (R1, R0) = (1, 0) which means R1 enabled and R0 disabled. ··· 151 150 mediatek,pull-down-adv: 152 151 description: | 153 152 Pull down settings for 2 pull resistors, R0 and R1. User can 154 - configure those special pins. Valid arguments are described as below: 153 + configure those special pins. Valid arguments are described as 154 + below: 155 155 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 156 156 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled. 157 157 2: (R1, R0) = (1, 0) which means R1 enabled and R0 disabled. ··· 161 159 enum: [0, 1, 2, 3] 162 160 163 161 mediatek,tdsel: 164 - description: | 162 + description: 165 163 An integer describing the steps for output level shifter duty 166 164 cycle when asserted (high pulse width adjustment). Valid arguments 167 165 are from 0 to 15. 168 166 $ref: /schemas/types.yaml#/definitions/uint32 169 167 170 168 mediatek,rdsel: 171 - description: | 169 + description: 172 170 An integer describing the steps for input level shifter duty cycle 173 171 when asserted (high pulse width adjustment). Valid arguments are 174 172 from 0 to 63.
+23 -24
Documentation/devicetree/bindings/pinctrl/mediatek,mt8186-pinctrl.yaml
··· 9 9 maintainers: 10 10 - Sean Wang <sean.wang@mediatek.com> 11 11 12 - description: | 12 + description: 13 13 The MediaTek's MT8186 Pin controller is used to control SoC pins. 14 14 15 15 properties: ··· 19 19 gpio-controller: true 20 20 21 21 '#gpio-cells': 22 - description: | 22 + description: 23 23 Number of cells in GPIO specifier. Since the generic GPIO binding is used, 24 - the amount of cells must be specified as 2. See the below 25 - mentioned gpio binding representation for description of particular cells. 24 + the amount of cells must be specified as 2. See the below mentioned gpio 25 + binding representation for description of particular cells. 26 26 const: 2 27 27 28 28 gpio-ranges: ··· 31 31 gpio-line-names: true 32 32 33 33 reg: 34 - description: | 35 - Physical address base for gpio base registers. There are 8 different GPIO 34 + description: 35 + Physical address base for GPIO base registers. There are 8 different GPIO 36 36 physical address base in mt8186. 37 37 maxItems: 8 38 38 39 39 reg-names: 40 - description: | 41 - Gpio base register names. 40 + description: 41 + GPIO base register names. 42 42 items: 43 43 - const: iocfg0 44 44 - const: iocfg_lt ··· 60 60 61 61 mediatek,rsel-resistance-in-si-unit: 62 62 type: boolean 63 - description: | 64 - Identifying i2c pins pull up/down type which is RSEL. It can support 65 - RSEL define or si unit value(ohm) to set different resistance. 63 + description: 64 + Identifying i2c pins pull up/down type which is RSEL. It can support RSEL 65 + define or si unit value(ohm) to set different resistance. 66 66 67 67 # PIN CONFIGURATION NODES 68 68 patternProperties: ··· 77 77 A pinctrl node should contain at least one subnodes representing the 78 78 pinctrl groups available on the machine. Each subnode will list the 79 79 pins it needs, and how they should be configured, with regard to muxer 80 - configuration, pullups, drive strength, input enable/disable and 81 - input schmitt. 80 + configuration, pullups, drive strength, input enable/disable and input 81 + schmitt. 82 82 An example of using macro: 83 83 pincontroller { 84 84 /* GPIO0 set as multifunction GPIO0 */ ··· 98 98 99 99 properties: 100 100 pinmux: 101 - description: | 101 + description: 102 102 Integer array, represents gpio pin number and mux setting. 103 103 Supported pin number and mux varies for different SoCs, and are 104 - defined as macros in dt-bindings/pinctrl/<soc>-pinfunc.h 105 - directly. 104 + defined as macros in dt-bindings/pinctrl/<soc>-pinfunc.h directly. 106 105 107 106 drive-strength: 108 107 enum: [2, 4, 6, 8, 10, 12, 14, 16] ··· 128 129 For pull down type is RSEL, it can add RSEL define & resistance 129 130 value(ohm) to set different resistance by identifying property 130 131 "mediatek,rsel-resistance-in-si-unit". 131 - It can support "MTK_PULL_SET_RSEL_000" & "MTK_PULL_SET_RSEL_001" 132 - & "MTK_PULL_SET_RSEL_010" & "MTK_PULL_SET_RSEL_011" 133 - define in mt8186. It can also support resistance value(ohm) 134 - "75000" & "5000" in mt8186. 132 + It can support "MTK_PULL_SET_RSEL_000" & "MTK_PULL_SET_RSEL_001" & 133 + "MTK_PULL_SET_RSEL_010" & "MTK_PULL_SET_RSEL_011" define in 134 + mt8186. It can also support resistance value(ohm) "75000" & "5000" 135 + in mt8186. 135 136 An example of using RSEL define: 136 137 pincontroller { 137 138 i2c0_pin { ··· 173 174 For pull up type is RSEL, it can add RSEL define & resistance 174 175 value(ohm) to set different resistance by identifying property 175 176 "mediatek,rsel-resistance-in-si-unit". 176 - It can support "MTK_PULL_SET_RSEL_000" & "MTK_PULL_SET_RSEL_001" 177 - & "MTK_PULL_SET_RSEL_010" & "MTK_PULL_SET_RSEL_011" 178 - define in mt8186. It can also support resistance value(ohm) 179 - "1000" & "5000" & "10000" & "75000" in mt8186. 177 + It can support "MTK_PULL_SET_RSEL_000" & "MTK_PULL_SET_RSEL_001" & 178 + "MTK_PULL_SET_RSEL_010" & "MTK_PULL_SET_RSEL_011" define in 179 + mt8186. It can also support resistance value(ohm) "1000" & "5000" 180 + & "10000" & "75000" in mt8186. 180 181 An example of using si unit resistance value(ohm): 181 182 &pio { 182 183 mediatek,rsel-resistance-in-si-unit;
+40 -34
Documentation/devicetree/bindings/pinctrl/mediatek,mt8188-pinctrl.yaml
··· 9 9 maintainers: 10 10 - Hui Liu <hui.liu@mediatek.com> 11 11 12 - description: | 12 + description: 13 13 The MediaTek's MT8188 Pin controller is used to control SoC pins. 14 14 15 15 properties: ··· 19 19 gpio-controller: true 20 20 21 21 '#gpio-cells': 22 - description: | 23 - Number of cells in GPIO specifier, should be two. The first cell 24 - is the pin number, the second cell is used to specify optional 25 - parameters which are defined in <dt-bindings/gpio/gpio.h>. 22 + description: 23 + Number of cells in GPIO specifier, should be two. The first cell is the 24 + pin number, the second cell is used to specify optional parameters which 25 + are defined in <dt-bindings/gpio/gpio.h>. 26 26 const: 2 27 27 28 28 gpio-ranges: ··· 59 59 60 60 mediatek,rsel-resistance-in-si-unit: 61 61 type: boolean 62 - description: | 63 - We provide two methods to select the resistance for I2C when pull up or pull down. 64 - The first is by RSEL definition value, another one is by resistance value(ohm). 65 - This flag is used to identify if the method is resistance(si unit) value. 62 + description: 63 + We provide two methods to select the resistance for I2C when pull up or 64 + pull down. The first is by RSEL definition value, another one is by 65 + resistance value(ohm). This flag is used to identify if the method is 66 + resistance(si unit) value. 66 67 67 68 # PIN CONFIGURATION NODES 68 69 patternProperties: ··· 76 75 type: object 77 76 $ref: "/schemas/pinctrl/pincfg-node.yaml" 78 77 additionalProperties: false 79 - description: | 78 + description: 80 79 A pinctrl node should contain at least one subnode representing the 81 80 pinctrl groups available on the machine. Each subnode will list the 82 81 pins it needs, and how they should be configured, with regard to muxer 83 - configuration, pullups, drive strength, input enable/disable and 84 - input schmitt. 82 + configuration, pullups, drive strength, input enable/disable and input 83 + schmitt. 85 84 86 85 properties: 87 86 pinmux: 88 - description: | 87 + description: 89 88 Integer array, represents gpio pin number and mux setting. 90 89 Supported pin number and mux varies for different SoCs, and are 91 90 defined as macros in dt-bindings/pinctrl/mediatek,<soc>-pinfunc.h ··· 107 106 - enum: [75000, 5000] 108 107 description: mt8188 pull down RSEL type si unit value(ohm). 109 108 description: | 110 - For pull down type is normal, it doesn't need add RSEL & R1R0 define 111 - and resistance value. 109 + For pull down type is normal, it doesn't need add RSEL & R1R0 110 + define and resistance value. 112 111 For pull down type is PUPD/R0/R1 type, it can add R1R0 define to 113 112 set different resistance. It can support "MTK_PUPD_SET_R1R0_00" & 114 - "MTK_PUPD_SET_R1R0_01" & "MTK_PUPD_SET_R1R0_10" & "MTK_PUPD_SET_R1R0_11" 115 - define in mt8188. 116 - For pull down type is RSEL, it can add RSEL define & resistance value(ohm) 117 - to set different resistance by identifying property "mediatek,rsel-resistance-in-si-unit". 118 - It can support "MTK_PULL_SET_RSEL_000" & "MTK_PULL_SET_RSEL_001" 119 - & "MTK_PULL_SET_RSEL_010" & "MTK_PULL_SET_RSEL_011" & "MTK_PULL_SET_RSEL_100" 120 - & "MTK_PULL_SET_RSEL_101" & "MTK_PULL_SET_RSEL_110" & "MTK_PULL_SET_RSEL_111" 121 - define in mt8188. It can also support resistance value(ohm) "75000" & "5000" in mt8188. 113 + "MTK_PUPD_SET_R1R0_01" & "MTK_PUPD_SET_R1R0_10" & 114 + "MTK_PUPD_SET_R1R0_11" define in mt8188. 115 + For pull down type is RSEL, it can add RSEL define & resistance 116 + value(ohm) to set different resistance by identifying property 117 + "mediatek,rsel-resistance-in-si-unit". It can support 118 + "MTK_PULL_SET_RSEL_000" & "MTK_PULL_SET_RSEL_001" & 119 + "MTK_PULL_SET_RSEL_010" & "MTK_PULL_SET_RSEL_011" & 120 + "MTK_PULL_SET_RSEL_100" & "MTK_PULL_SET_RSEL_101" & 121 + "MTK_PULL_SET_RSEL_110" & "MTK_PULL_SET_RSEL_111" define in 122 + mt8188. It can also support resistance value(ohm) "75000" & "5000" 123 + in mt8188. 122 124 123 125 bias-pull-up: 124 126 oneOf: ··· 135 131 description: | 136 132 For pull up type is normal, it don't need add RSEL & R1R0 define 137 133 and resistance value. 138 - For pull up type is PUPD/R0/R1 type, it can add R1R0 define to 139 - set different resistance. It can support "MTK_PUPD_SET_R1R0_00" & 140 - "MTK_PUPD_SET_R1R0_01" & "MTK_PUPD_SET_R1R0_10" & "MTK_PUPD_SET_R1R0_11" 141 - define in mt8188. 142 - For pull up type is RSEL, it can add RSEL define & resistance value(ohm) 143 - to set different resistance by identifying property "mediatek,rsel-resistance-in-si-unit". 144 - It can support "MTK_PULL_SET_RSEL_000" & "MTK_PULL_SET_RSEL_001" 145 - & "MTK_PULL_SET_RSEL_010" & "MTK_PULL_SET_RSEL_011" & "MTK_PULL_SET_RSEL_100" 146 - & "MTK_PULL_SET_RSEL_101" & "MTK_PULL_SET_RSEL_110" & "MTK_PULL_SET_RSEL_111" 147 - define in mt8188. It can also support resistance value(ohm) 148 - "1000" & "1500" & "2000" & "3000" & "4000" & "5000" & "10000" & "75000" in mt8188. 134 + For pull up type is PUPD/R0/R1 type, it can add R1R0 define to set 135 + different resistance. It can support "MTK_PUPD_SET_R1R0_00" & 136 + "MTK_PUPD_SET_R1R0_01" & "MTK_PUPD_SET_R1R0_10" & 137 + "MTK_PUPD_SET_R1R0_11" define in mt8188. 138 + For pull up type is RSEL, it can add RSEL define & resistance 139 + value(ohm) to set different resistance by identifying property 140 + "mediatek,rsel-resistance-in-si-unit". It can support 141 + "MTK_PULL_SET_RSEL_000" & "MTK_PULL_SET_RSEL_001" & 142 + "MTK_PULL_SET_RSEL_010" & "MTK_PULL_SET_RSEL_011" & 143 + "MTK_PULL_SET_RSEL_100" & "MTK_PULL_SET_RSEL_101" & 144 + "MTK_PULL_SET_RSEL_110" & "MTK_PULL_SET_RSEL_111" define in 145 + mt8188. It can also support resistance value(ohm) "1000" & "1500" 146 + & "2000" & "3000" & "4000" & "5000" & "10000" & "75000" in mt8188. 149 147 150 148 bias-disable: true 151 149
+24 -23
Documentation/devicetree/bindings/pinctrl/mediatek,mt8192-pinctrl.yaml
··· 9 9 maintainers: 10 10 - Sean Wang <sean.wang@mediatek.com> 11 11 12 - description: | 12 + description: 13 13 The MediaTek's MT8192 Pin controller is used to control SoC pins. 14 14 15 15 properties: ··· 19 19 gpio-controller: true 20 20 21 21 '#gpio-cells': 22 - description: | 22 + description: 23 23 Number of cells in GPIO specifier. Since the generic GPIO binding is used, 24 - the amount of cells must be specified as 2. See the below 25 - mentioned gpio binding representation for description of particular cells. 24 + the amount of cells must be specified as 2. See the below mentioned gpio 25 + binding representation for description of particular cells. 26 26 const: 2 27 27 28 28 gpio-ranges: 29 - description: gpio valid number range. 29 + description: GPIO valid number range. 30 30 maxItems: 1 31 31 32 32 gpio-line-names: true 33 33 34 34 reg: 35 - description: | 36 - Physical address base for gpio base registers. There are 11 GPIO 37 - physical address base in mt8192. 35 + description: 36 + Physical address base for GPIO base registers. There are 11 GPIO physical 37 + address base in mt8192. 38 38 maxItems: 11 39 39 40 40 reg-names: 41 - description: | 42 - Gpio base register names. 41 + description: 42 + GPIO base register names. 43 43 maxItems: 11 44 44 45 45 interrupt-controller: true ··· 59 59 patternProperties: 60 60 '^pins': 61 61 type: object 62 - description: | 62 + description: 63 63 A pinctrl node should contain at least one subnodes representing the 64 64 pinctrl groups available on the machine. Each subnode will list the 65 65 pins it needs, and how they should be configured, with regard to muxer 66 - configuration, pullups, drive strength, input enable/disable and 67 - input schmitt. 66 + configuration, pullups, drive strength, input enable/disable and input 67 + schmitt. 68 68 $ref: "pinmux-node.yaml" 69 69 70 70 properties: 71 71 pinmux: 72 - description: | 72 + description: 73 73 Integer array, represents gpio pin number and mux setting. 74 - Supported pin number and mux varies for different SoCs, and are defined 75 - as macros in dt-bindings/pinctrl/<soc>-pinfunc.h directly. 74 + Supported pin number and mux varies for different SoCs, and are 75 + defined as macros in dt-bindings/pinctrl/<soc>-pinfunc.h directly. 76 76 77 77 drive-strength: 78 - description: | 79 - It can support some arguments, such as MTK_DRIVE_4mA, MTK_DRIVE_6mA, etc. See 80 - dt-bindings/pinctrl/mt65xx.h. It can only support 2/4/6/8/10/12/14/16mA in mt8192. 78 + description: 79 + It can support some arguments, such as MTK_DRIVE_4mA, 80 + MTK_DRIVE_6mA, etc. See dt-bindings/pinctrl/mt65xx.h. It can only 81 + support 2/4/6/8/10/12/14/16mA in mt8192. 81 82 enum: [2, 4, 6, 8, 10, 12, 14, 16] 82 83 83 84 drive-strength-microamp: ··· 92 91 description: PUPD/R1/R0 pull down type. See MTK_PUPD_SET_R1R0_ 93 92 defines in dt-bindings/pinctrl/mt65xx.h. 94 93 - enum: [200, 201, 202, 203] 95 - description: RSEL pull down type. See MTK_PULL_SET_RSEL_ 96 - defines in dt-bindings/pinctrl/mt65xx.h. 94 + description: RSEL pull down type. See MTK_PULL_SET_RSEL_ defines 95 + in dt-bindings/pinctrl/mt65xx.h. 97 96 98 97 bias-pull-up: 99 98 oneOf: ··· 103 102 description: PUPD/R1/R0 pull up type. See MTK_PUPD_SET_R1R0_ 104 103 defines in dt-bindings/pinctrl/mt65xx.h. 105 104 - enum: [200, 201, 202, 203] 106 - description: RSEL pull up type. See MTK_PULL_SET_RSEL_ 107 - defines in dt-bindings/pinctrl/mt65xx.h. 105 + description: RSEL pull up type. See MTK_PULL_SET_RSEL_ defines 106 + in dt-bindings/pinctrl/mt65xx.h. 108 107 109 108 bias-disable: true 110 109
+20 -21
Documentation/devicetree/bindings/pinctrl/mediatek,mt8195-pinctrl.yaml
··· 9 9 maintainers: 10 10 - Sean Wang <sean.wang@mediatek.com> 11 11 12 - description: | 12 + description: 13 13 The MediaTek's MT8195 Pin controller is used to control SoC pins. 14 14 15 15 properties: ··· 19 19 gpio-controller: true 20 20 21 21 '#gpio-cells': 22 - description: | 22 + description: 23 23 Number of cells in GPIO specifier. Since the generic GPIO binding is used, 24 - the amount of cells must be specified as 2. See the below 25 - mentioned gpio binding representation for description of particular cells. 24 + the amount of cells must be specified as 2. See the below mentioned gpio 25 + binding representation for description of particular cells. 26 26 const: 2 27 27 28 28 gpio-ranges: 29 - description: gpio valid number range. 29 + description: GPIO valid number range. 30 30 maxItems: 1 31 31 32 32 gpio-line-names: true 33 33 34 34 reg: 35 - description: | 36 - Physical address base for gpio base registers. There are 8 GPIO 37 - physical address base in mt8195. 35 + description: 36 + Physical address base for GPIO base registers. There are 8 GPIO physical 37 + address base in mt8195. 38 38 maxItems: 8 39 39 40 40 reg-names: 41 - description: | 42 - Gpio base register names. 41 + description: 42 + GPIO base register names. 43 43 maxItems: 8 44 44 45 45 interrupt-controller: true ··· 53 53 54 54 mediatek,rsel-resistance-in-si-unit: 55 55 type: boolean 56 - description: | 57 - Identifying i2c pins pull up/down type which is RSEL. It can support 58 - RSEL define or si unit value(ohm) to set different resistance. 56 + description: 57 + Identifying i2c pins pull up/down type which is RSEL. It can support RSEL 58 + define or si unit value(ohm) to set different resistance. 59 59 60 60 # PIN CONFIGURATION NODES 61 61 patternProperties: ··· 70 70 A pinctrl node should contain at least one subnodes representing the 71 71 pinctrl groups available on the machine. Each subnode will list the 72 72 pins it needs, and how they should be configured, with regard to muxer 73 - configuration, pullups, drive strength, input enable/disable and 74 - input schmitt. 73 + configuration, pullups, drive strength, input enable/disable and input 74 + schmitt. 75 75 An example of using macro: 76 76 pincontroller { 77 77 /* GPIO0 set as multifunction GPIO0 */ ··· 91 91 92 92 properties: 93 93 pinmux: 94 - description: | 94 + description: 95 95 Integer array, represents gpio pin number and mux setting. 96 96 Supported pin number and mux varies for different SoCs, and are 97 - defined as macros in dt-bindings/pinctrl/<soc>-pinfunc.h 98 - directly. 97 + defined as macros in dt-bindings/pinctrl/<soc>-pinfunc.h directly. 99 98 100 99 drive-strength: 101 100 enum: [2, 4, 6, 8, 10, 12, 14, 16] ··· 173 174 & "MTK_PULL_SET_RSEL_010" & "MTK_PULL_SET_RSEL_011" 174 175 & "MTK_PULL_SET_RSEL_100" & "MTK_PULL_SET_RSEL_101" 175 176 & "MTK_PULL_SET_RSEL_110" & "MTK_PULL_SET_RSEL_111" 176 - define in mt8195. It can also support resistance value(ohm) 177 - "1000" & "1500" & "2000" & "3000" & "4000" & "5000" & "10000" & 178 - "75000" in mt8195. 177 + define in mt8195. It can also support resistance value(ohm) "1000" 178 + & "1500" & "2000" & "3000" & "4000" & "5000" & "10000" & "75000" 179 + in mt8195. 179 180 An example of using RSEL define: 180 181 pincontroller { 181 182 i2c0-pins {
+15 -13
Documentation/devicetree/bindings/pinctrl/mediatek,mt8365-pinctrl.yaml
··· 10 10 - Zhiyong Tao <zhiyong.tao@mediatek.com> 11 11 - Bernhard Rosenkränzer <bero@baylibre.com> 12 12 13 - description: | 13 + description: 14 14 The MediaTek's MT8365 Pin controller is used to control SoC pins. 15 15 16 16 properties: ··· 26 26 maxItems: 1 27 27 minItems: 1 28 28 maxItems: 2 29 - description: | 29 + description: 30 30 Should be phandles of the syscfg node. 31 31 32 32 gpio-controller: true 33 33 34 34 "#gpio-cells": 35 35 const: 2 36 - description: | 37 - Number of cells in GPIO specifier. Since the generic GPIO 38 - binding is used, the amount of cells must be specified as 2. See the below 39 - mentioned gpio binding representation for description of particular cells. 36 + description: 37 + Number of cells in GPIO specifier. Since the generic GPIO binding is used, 38 + the amount of cells must be specified as 2. See the below mentioned gpio 39 + binding representation for description of particular cells. 40 40 41 41 interrupt-controller: true 42 42 ··· 54 54 "pins$": 55 55 type: object 56 56 additionalProperties: false 57 - description: | 57 + description: 58 58 A pinctrl node should contain at least one subnode representing the 59 59 pinctrl groups available on the machine. Each subnode will list the 60 60 pins it needs, and how they should be configured, with regard to muxer ··· 65 65 properties: 66 66 pinmux: 67 67 description: 68 - integer array, represents gpio pin number and mux setting. 68 + Integer array, represents gpio pin number and mux setting. 69 69 Supported pin number and mux varies for different SoCs, and are 70 70 defined as macros in <soc>-pinfunc.h directly. 71 71 72 72 bias-disable: true 73 73 74 74 bias-pull-up: 75 - description: | 75 + description: 76 76 Besides generic pinconfig options, it can be used as the pull up 77 77 settings for 2 pull resistors, R0 and R1. User can configure those 78 78 special pins. ··· 120 120 mediatek,pull-up-adv: 121 121 description: | 122 122 Pull up setings for 2 pull resistors, R0 and R1. User can 123 - configure those special pins. Valid arguments are described as below: 123 + configure those special pins. Valid arguments are described as 124 + below: 124 125 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 125 126 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled. 126 127 2: (R1, R0) = (1, 0) which means R1 enabled and R0 disabled. ··· 132 131 mediatek,pull-down-adv: 133 132 description: | 134 133 Pull down settings for 2 pull resistors, R0 and R1. User can 135 - configure those special pins. Valid arguments are described as below: 134 + configure those special pins. Valid arguments are described as 135 + below: 136 136 0: (R1, R0) = (0, 0) which means R1 disabled and R0 disabled. 137 137 1: (R1, R0) = (0, 1) which means R1 disabled and R0 enabled. 138 138 2: (R1, R0) = (1, 0) which means R1 enabled and R0 disabled. ··· 142 140 enum: [0, 1, 2, 3] 143 141 144 142 mediatek,tdsel: 145 - description: | 143 + description: 146 144 An integer describing the steps for output level shifter duty 147 145 cycle when asserted (high pulse width adjustment). Valid arguments 148 146 are from 0 to 15. 149 147 $ref: /schemas/types.yaml#/definitions/uint32 150 148 151 149 mediatek,rdsel: 152 - description: | 150 + description: 153 151 An integer describing the steps for input level shifter duty cycle 154 152 when asserted (high pulse width adjustment). Valid arguments are 155 153 from 0 to 63.
+1 -1
Documentation/devicetree/bindings/pinctrl/ralink,rt2880-pinctrl.yaml
··· 10 10 - Arınç ÜNAL <arinc.unal@arinc9.com> 11 11 - Sergio Paracuellos <sergio.paracuellos@gmail.com> 12 12 13 - description: 13 + description: | 14 14 Ralink RT2880 pin controller for RT2880 SoC. 15 15 The pin controller can only set the muxing of pin groups. Muxing individual 16 16 pins is not supported. There is no pinconf support.
+1 -1
Documentation/devicetree/bindings/pinctrl/ralink,rt305x-pinctrl.yaml
··· 10 10 - Arınç ÜNAL <arinc.unal@arinc9.com> 11 11 - Sergio Paracuellos <sergio.paracuellos@gmail.com> 12 12 13 - description: 13 + description: | 14 14 Ralink RT305X pin controller for RT3050, RT3052, RT3350, RT3352 and RT5350 15 15 SoCs. 16 16 The pin controller can only set the muxing of pin groups. Muxing individual
+1 -1
Documentation/devicetree/bindings/pinctrl/ralink,rt3883-pinctrl.yaml
··· 10 10 - Arınç ÜNAL <arinc.unal@arinc9.com> 11 11 - Sergio Paracuellos <sergio.paracuellos@gmail.com> 12 12 13 - description: 13 + description: | 14 14 Ralink RT3883 pin controller for RT3883 SoC. 15 15 The pin controller can only set the muxing of pin groups. Muxing individual 16 16 pins is not supported. There is no pinconf support.