History

Merge tag 'devicetree-fixes-for-5.6-3' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux

Pull devicetree fixes from Rob Herring: "Another batch of DT fixes. I think this should be the last of it, but sending pull requests seems to cause people to send more fixes. Summary: - Fixes for warnings introduced by hierarchical PSCI binding changes - Fixes for broken doc references due to DT schema conversions - Several grammar and typo fixes - Fix a bunch of dtc warnings in examples" * tag 'devicetree-fixes-for-5.6-3' of git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux: dt-bindings: arm: Fixup the DT bindings for hierarchical PSCI states dt-bindings: power: Extend nodename pattern for power-domain providers MAINTAINERS: update ALLWINNER CPUFREQ DRIVER entry dt-bindings: bus: Drop empty compatible string in example dt-bindings: power: Convert domain-idle-states bindings to json-schema dt-bindings: arm: Fix cpu compatibles in the hierarchical example for PSCI dt-bindings: arm: Correct links to idle states definitions dt-bindings: mfd: Fix typo in file name of twl-familly.txt dt-bindings: mfd: tps65910: Improve grammar dt-bindings: mfd: zii,rave-sp: Fix a typo ("onborad") dt-bindings: arm: fsl: fix APF6Dev compatible dt-bindings: Fix dtc warnings in examples docs: dt: fix several broken doc references docs: dt: fix several broken references due to renames MAINTAINERS: clean up PCIE DRIVER FOR CAVIUM THUNDERX

Linus Torvalds committed 6 years ago

Commit bdf1ea72 parents 2f501bb d2334a959 files · +169 −163Browse files

Unified · Split

59 files
  1. Documentation/devicetree/bindings/arm/arm,scmi.txt +1 −1
  2. Documentation/devicetree/bindings/arm/arm,scpi.txt +1 −1
  3. Documentation/devicetree/bindings/arm/bcm/brcm,bcm63138.txt +1 −1
  4. Documentation/devicetree/bindings/arm/cpus.yaml +1 −1
  5. Documentation/devicetree/bindings/arm/fsl.yaml +1 −1
  6. Documentation/devicetree/bindings/arm/hisilicon/hi3519-sysctrl.txt +1 −1
  7. Documentation/devicetree/bindings/arm/msm/qcom,idle-state.txt +1 −1
  8. Documentation/devicetree/bindings/arm/omap/mpu.txt +1 −1
  9. Documentation/devicetree/bindings/arm/psci.yaml +17 −19
  10. Documentation/devicetree/bindings/arm/stm32/st,mlahb.yaml +1 −1
  11. Documentation/devicetree/bindings/bus/allwinner,sun8i-a23-rsb.yaml +0 −1
  12. Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-osc-clk.yaml +1 −1
  13. Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-gt-clk.yaml +1 −1
  14. Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml +1 −1
  15. Documentation/devicetree/bindings/display/allwinner,sun4i-a10-tv-encoder.yaml +1 −5
  16. Documentation/devicetree/bindings/display/bridge/anx6345.yaml +2 −8
  17. Documentation/devicetree/bindings/display/panel/leadtek,ltk500hd1829.yaml +2 −0
  18. Documentation/devicetree/bindings/display/panel/xinpeng,xpp055c272.yaml +2 −0
  19. Documentation/devicetree/bindings/display/simple-framebuffer.yaml +1 −5
  20. Documentation/devicetree/bindings/display/tilcdc/tilcdc.txt +1 −1
  21. Documentation/devicetree/bindings/dma/ti/k3-udma.yaml +1 −13
  22. Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml +7 −7
  23. Documentation/devicetree/bindings/gpu/arm,mali-midgard.yaml +7 −7
  24. Documentation/devicetree/bindings/iio/adc/samsung,exynos-adc.yaml +1 −1
  25. Documentation/devicetree/bindings/input/touchscreen/goodix.yaml +1 −1
  26. Documentation/devicetree/bindings/input/twl4030-pwrbutton.txt +1 −1
  27. Documentation/devicetree/bindings/leds/common.yaml +1 −1
  28. Documentation/devicetree/bindings/leds/register-bit-led.txt +1 −1
  29. Documentation/devicetree/bindings/media/ti,cal.yaml +1 −1
  30. Documentation/devicetree/bindings/memory-controllers/ti/emif.txt +1 −1
  31. Documentation/devicetree/bindings/mfd/max77650.yaml +2 −2
  32. Documentation/devicetree/bindings/mfd/tps65910.txt +2 −2
  33. Documentation/devicetree/bindings/mfd/twl-family.txt +0 −0
  34. Documentation/devicetree/bindings/mfd/zii,rave-sp.txt +1 −1
  35. Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt +1 −1
  36. Documentation/devicetree/bindings/mmc/mmc-controller.yaml +1 −0
  37. Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt +1 −1
  38. Documentation/devicetree/bindings/net/brcm,bcm7445-switch-v4.0.txt +1 −1
  39. Documentation/devicetree/bindings/nvmem/nvmem.yaml +2 −0
  40. Documentation/devicetree/bindings/phy/allwinner,sun4i-a10-usb-phy.yaml +1 −1
  41. Documentation/devicetree/bindings/pinctrl/aspeed,ast2400-pinctrl.yaml +1 −1
  42. Documentation/devicetree/bindings/pinctrl/aspeed,ast2500-pinctrl.yaml +1 −1
  43. Documentation/devicetree/bindings/pinctrl/aspeed,ast2600-pinctrl.yaml +1 −1
  44. Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml +1 −1
  45. Documentation/devicetree/bindings/power/amlogic,meson-ee-pwrc.yaml +1 −1
  46. Documentation/devicetree/bindings/power/domain-idle-state.txt +0 −33
  47. Documentation/devicetree/bindings/power/domain-idle-state.yaml +64 −0
  48. Documentation/devicetree/bindings/power/power-domain.yaml +11 −13
  49. Documentation/devicetree/bindings/power/power_domain.txt +1 −1
  50. Documentation/devicetree/bindings/regulator/regulator.yaml +1 −1
  51. Documentation/devicetree/bindings/reset/st,stm32mp1-rcc.txt +1 −1
  52. Documentation/devicetree/bindings/sound/st,stm32-sai.txt +1 −1
  53. Documentation/devicetree/bindings/sound/st,stm32-spdifrx.txt +1 −1
  54. Documentation/devicetree/bindings/spi/st,stm32-spi.yaml +1 −1
  55. Documentation/devicetree/bindings/sram/allwinner,sun4i-a10-system-control.yaml +1 −1
  56. Documentation/devicetree/bindings/thermal/brcm,avs-ro-thermal.yaml +1 −1
  57. Documentation/devicetree/bindings/timer/allwinner,sun4i-a10-timer.yaml +1 −1
  58. MAINTAINERS +7 −8
  59. drivers/staging/wfx/Documentation/devicetree/bindings/net/wireless/siliabs,wfx.txt +1 −1
Documentation/devicetree/bindings/arm/arm,scmi.txt+1−1
@@ -102,7 +102,7 @@ Required sub-node properties: · 101 unmodified lines
102[1] Documentation/devicetree/bindings/clock/clock-bindings.txt102[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
103[2] Documentation/devicetree/bindings/power/power-domain.yaml103[2] Documentation/devicetree/bindings/power/power-domain.yaml
104[3] Documentation/devicetree/bindings/thermal/thermal.txt104[3] Documentation/devicetree/bindings/thermal/thermal.txt
105[4] Documentation/devicetree/bindings/sram/sram.txt105[4] Documentation/devicetree/bindings/sram/sram.yaml
106[5] Documentation/devicetree/bindings/reset/reset.txt106[5] Documentation/devicetree/bindings/reset/reset.txt
107 107
108Example:108Example:
Documentation/devicetree/bindings/arm/arm,scpi.txt+1−1
@@ -109,7 +109,7 @@ Required properties: · 108 unmodified lines
109[0] http://infocenter.arm.com/help/topic/com.arm.doc.dui0922b/index.html109[0] http://infocenter.arm.com/help/topic/com.arm.doc.dui0922b/index.html
110[1] Documentation/devicetree/bindings/clock/clock-bindings.txt110[1] Documentation/devicetree/bindings/clock/clock-bindings.txt
111[2] Documentation/devicetree/bindings/thermal/thermal.txt111[2] Documentation/devicetree/bindings/thermal/thermal.txt
112[3] Documentation/devicetree/bindings/sram/sram.txt112[3] Documentation/devicetree/bindings/sram/sram.yaml
113[4] Documentation/devicetree/bindings/power/power-domain.yaml113[4] Documentation/devicetree/bindings/power/power-domain.yaml
114 114
115Example:115Example:
Documentation/devicetree/bindings/arm/bcm/brcm,bcm63138.txt+1−1
@@ -62,7 +62,7 @@ Timer node: · 61 unmodified lines
62 62
63Syscon reboot node:63Syscon reboot node:
64 64
65See Documentation/devicetree/bindings/power/reset/syscon-reboot.txt for the65See Documentation/devicetree/bindings/power/reset/syscon-reboot.yaml for the
66detailed list of properties, the two values defined below are specific to the66detailed list of properties, the two values defined below are specific to the
67BCM6328-style timer:67BCM6328-style timer:
68 68
Documentation/devicetree/bindings/arm/cpus.yaml+1−1
@@ -216,7 +216,7 @@ properties: · 215 unmodified lines
216 $ref: '/schemas/types.yaml#/definitions/phandle-array'216 $ref: '/schemas/types.yaml#/definitions/phandle-array'
217 description: |217 description: |
218 List of phandles to idle state nodes supported218 List of phandles to idle state nodes supported
219 by this cpu (see ./idle-states.txt).219 by this cpu (see ./idle-states.yaml).
220 220
221 capacity-dmips-mhz:221 capacity-dmips-mhz:
222 $ref: '/schemas/types.yaml#/definitions/uint32'222 $ref: '/schemas/types.yaml#/definitions/uint32'
Documentation/devicetree/bindings/arm/fsl.yaml+1−1
@@ -160,7 +160,7 @@ properties: · 159 unmodified lines
160 items:160 items:
161 - enum:161 - enum:
162 - armadeus,imx6dl-apf6 # APF6 (Solo) SoM162 - armadeus,imx6dl-apf6 # APF6 (Solo) SoM
163 - armadeus,imx6dl-apf6dldev # APF6 (Solo) SoM on APF6Dev board163 - armadeus,imx6dl-apf6dev # APF6 (Solo) SoM on APF6Dev board
164 - eckelmann,imx6dl-ci4x10164 - eckelmann,imx6dl-ci4x10
165 - emtrion,emcon-mx6 # emCON-MX6S or emCON-MX6DL SoM165 - emtrion,emcon-mx6 # emCON-MX6S or emCON-MX6DL SoM
166 - emtrion,emcon-mx6-avari # emCON-MX6S or emCON-MX6DL SoM on Avari Base166 - emtrion,emcon-mx6-avari # emCON-MX6S or emCON-MX6DL SoM on Avari Base
Documentation/devicetree/bindings/arm/hisilicon/hi3519-sysctrl.txt+1−1
@@ -1,7 +1,7 @@
1* Hisilicon Hi3519 System Controller Block1* Hisilicon Hi3519 System Controller Block
2 2
3This bindings use the following binding:3This bindings use the following binding:
4Documentation/devicetree/bindings/mfd/syscon.txt4Documentation/devicetree/bindings/mfd/syscon.yaml
5 5
6Required properties:6Required properties:
7- compatible: "hisilicon,hi3519-sysctrl".7- compatible: "hisilicon,hi3519-sysctrl".
Documentation/devicetree/bindings/arm/msm/qcom,idle-state.txt+1−1
@@ -81,4 +81,4 @@ Example: · 80 unmodified lines
81 };81 };
82 };82 };
83 83
84[1]. Documentation/devicetree/bindings/arm/idle-states.txt84[1]. Documentation/devicetree/bindings/arm/idle-states.yaml
Documentation/devicetree/bindings/arm/omap/mpu.txt+1−1
@@ -17,7 +17,7 @@ am335x and am437x only: · 16 unmodified lines
17- pm-sram: Phandles to ocmcram nodes to be used for power management.17- pm-sram: Phandles to ocmcram nodes to be used for power management.
18 First should be type 'protect-exec' for the driver to use to copy18 First should be type 'protect-exec' for the driver to use to copy
19 and run PM functions, second should be regular pool to be used for19 and run PM functions, second should be regular pool to be used for
20 data region for code. See Documentation/devicetree/bindings/sram/sram.txt20 data region for code. See Documentation/devicetree/bindings/sram/sram.yaml
21 for more details.21 for more details.
22 22
23Examples:23Examples:
Documentation/devicetree/bindings/arm/psci.yaml+17−19
@@ -100,13 +100,14 @@ properties: · 99 unmodified lines
100 bindings in [1]) must specify this property.100 bindings in [1]) must specify this property.
101 101
102 [1] Kernel documentation - ARM idle states bindings102 [1] Kernel documentation - ARM idle states bindings
103 Documentation/devicetree/bindings/arm/idle-states.txt103 Documentation/devicetree/bindings/arm/idle-states.yaml
104
105 "#power-domain-cells":
106 description:
107 The number of cells in a PM domain specifier as per binding in [3].
108 Must be 0 as to represent a single PM domain.
109 104
105patternProperties:
106 "^power-domain-":
107 allOf:
108 - $ref: "../power/power-domain.yaml#"
109 type: object
110 description: |
110 ARM systems can have multiple cores, sometimes in an hierarchical111 ARM systems can have multiple cores, sometimes in an hierarchical
111 arrangement. This often, but not always, maps directly to the processor112 arrangement. This often, but not always, maps directly to the processor
112 power topology of the system. Individual nodes in a topology have their113 power topology of the system. Individual nodes in a topology have their
@@ -122,14 +123,8 @@ properties: · 9 unmodified lines
122 helps to implement support for OSI mode and OS implementations may choose123 helps to implement support for OSI mode and OS implementations may choose
123 to mandate it.124 to mandate it.
124 125
125 [3] Documentation/devicetree/bindings/power/power_domain.txt126 [3] Documentation/devicetree/bindings/power/power-domain.yaml
126 [4] Documentation/devicetree/bindings/power/domain-idle-state.txt127 [4] Documentation/devicetree/bindings/power/domain-idle-state.yaml
127
128 power-domains:
129 $ref: '/schemas/types.yaml#/definitions/phandle-array'
130 description:
131 List of phandles and PM domain specifiers, as defined by bindings of the
132 PM domain provider.
133 128
134required:129required:
135 - compatible130 - compatible
@@ -199,7 +194,7 @@ examples: · 63 unmodified lines
199 194
200 CPU0: cpu@0 {195 CPU0: cpu@0 {
201 device_type = "cpu";196 device_type = "cpu";
202 compatible = "arm,cortex-a53", "arm,armv8";197 compatible = "arm,cortex-a53";
203 reg = <0x0>;198 reg = <0x0>;
204 enable-method = "psci";199 enable-method = "psci";
205 power-domains = <&CPU_PD0>;200 power-domains = <&CPU_PD0>;
@@ -208,7 +203,7 @@ examples: · 2 unmodified lines
208 203
209 CPU1: cpu@1 {204 CPU1: cpu@1 {
210 device_type = "cpu";205 device_type = "cpu";
211 compatible = "arm,cortex-a57", "arm,armv8";206 compatible = "arm,cortex-a53";
212 reg = <0x100>;207 reg = <0x100>;
213 enable-method = "psci";208 enable-method = "psci";
214 power-domains = <&CPU_PD1>;209 power-domains = <&CPU_PD1>;
@@ -224,6 +219,9 @@ examples: · 9 unmodified lines
224 exit-latency-us = <10>;219 exit-latency-us = <10>;
225 min-residency-us = <100>;220 min-residency-us = <100>;
226 };221 };
222 };
223
224 domain-idle-states {
227 225
228 CLUSTER_RET: cluster-retention {226 CLUSTER_RET: cluster-retention {
229 compatible = "domain-idle-state";227 compatible = "domain-idle-state";
@@ -247,19 +245,19 @@ examples: · 17 unmodified lines
247 compatible = "arm,psci-1.0";245 compatible = "arm,psci-1.0";
248 method = "smc";246 method = "smc";
249 247
250 CPU_PD0: cpu-pd0 {248 CPU_PD0: power-domain-cpu0 {
251 #power-domain-cells = <0>;249 #power-domain-cells = <0>;
252 domain-idle-states = <&CPU_PWRDN>;250 domain-idle-states = <&CPU_PWRDN>;
253 power-domains = <&CLUSTER_PD>;251 power-domains = <&CLUSTER_PD>;
254 };252 };
255 253
256 CPU_PD1: cpu-pd1 {254 CPU_PD1: power-domain-cpu1 {
257 #power-domain-cells = <0>;255 #power-domain-cells = <0>;
258 domain-idle-states = <&CPU_PWRDN>;256 domain-idle-states = <&CPU_PWRDN>;
259 power-domains = <&CLUSTER_PD>;257 power-domains = <&CLUSTER_PD>;
260 };258 };
261 259
262 CLUSTER_PD: cluster-pd {260 CLUSTER_PD: power-domain-cluster {
263 #power-domain-cells = <0>;261 #power-domain-cells = <0>;
264 domain-idle-states = <&CLUSTER_RET>, <&CLUSTER_PWRDN>;262 domain-idle-states = <&CLUSTER_RET>, <&CLUSTER_PWRDN>;
265 };263 };
Documentation/devicetree/bindings/arm/stm32/st,mlahb.yaml+1−1
@@ -52,7 +52,7 @@ required: · 51 unmodified lines
52 52
53examples:53examples:
54 - |54 - |
55 mlahb: ahb {55 mlahb: ahb@38000000 {
56 compatible = "st,mlahb", "simple-bus";56 compatible = "st,mlahb", "simple-bus";
57 #address-cells = <1>;57 #address-cells = <1>;
58 #size-cells = <1>;58 #size-cells = <1>;
Documentation/devicetree/bindings/bus/allwinner,sun8i-a23-rsb.yaml+0−1
@@ -70,7 +70,6 @@ examples: · 69 unmodified lines
70 #size-cells = <0>;70 #size-cells = <0>;
71 71
72 pmic@3e3 {72 pmic@3e3 {
73 compatible = "...";
74 reg = <0x3e3>;73 reg = <0x3e3>;
75 74
76 /* ... */75 /* ... */
Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-osc-clk.yaml+1−1
@@ -40,7 +40,7 @@ additionalProperties: false · 39 unmodified lines
40 40
41examples:41examples:
42 - |42 - |
43 osc24M: clk@01c20050 {43 osc24M: clk@1c20050 {
44 #clock-cells = <0>;44 #clock-cells = <0>;
45 compatible = "allwinner,sun4i-a10-osc-clk";45 compatible = "allwinner,sun4i-a10-osc-clk";
46 reg = <0x01c20050 0x4>;46 reg = <0x01c20050 0x4>;
Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-gt-clk.yaml+1−1
@@ -41,7 +41,7 @@ additionalProperties: false · 40 unmodified lines
41 41
42examples:42examples:
43 - |43 - |
44 clk@0600005c {44 clk@600005c {
45 #clock-cells = <0>;45 #clock-cells = <0>;
46 compatible = "allwinner,sun9i-a80-gt-clk";46 compatible = "allwinner,sun9i-a80-gt-clk";
47 reg = <0x0600005c 0x4>;47 reg = <0x0600005c 0x4>;
Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml+1−1
@@ -42,7 +42,7 @@ properties: · 41 unmodified lines
42 be part of GCC and hence the TSENS properties can also be part42 be part of GCC and hence the TSENS properties can also be part
43 of the GCC/clock-controller node.43 of the GCC/clock-controller node.
44 For more details on the TSENS properties please refer44 For more details on the TSENS properties please refer
45 Documentation/devicetree/bindings/thermal/qcom-tsens.txt45 Documentation/devicetree/bindings/thermal/qcom-tsens.yaml
46 46
47 nvmem-cell-names:47 nvmem-cell-names:
48 minItems: 148 minItems: 1
Documentation/devicetree/bindings/display/allwinner,sun4i-a10-tv-encoder.yaml+1−5
@@ -49,11 +49,7 @@ examples: · 48 unmodified lines
49 resets = <&tcon_ch0_clk 0>;49 resets = <&tcon_ch0_clk 0>;
50 50
51 port {51 port {
52 #address-cells = <1>;52 tve0_in_tcon0: endpoint {
53 #size-cells = <0>;
54
55 tve0_in_tcon0: endpoint@0 {
56 reg = <0>;
57 remote-endpoint = <&tcon0_out_tve0>;53 remote-endpoint = <&tcon0_out_tve0>;
58 };54 };
59 };55 };
Documentation/devicetree/bindings/display/bridge/anx6345.yaml+2−8
@@ -79,21 +79,15 @@ examples: · 78 unmodified lines
79 #size-cells = <0>;79 #size-cells = <0>;
80 80
81 anx6345_in: port@0 {81 anx6345_in: port@0 {
82 #address-cells = <1>;
83 #size-cells = <0>;
84 reg = <0>;82 reg = <0>;
85 anx6345_in_tcon0: endpoint@0 {83 anx6345_in_tcon0: endpoint {
86 reg = <0>;
87 remote-endpoint = <&tcon0_out_anx6345>;84 remote-endpoint = <&tcon0_out_anx6345>;
88 };85 };
89 };86 };
90 87
91 anx6345_out: port@1 {88 anx6345_out: port@1 {
92 #address-cells = <1>;
93 #size-cells = <0>;
94 reg = <1>;89 reg = <1>;
95 anx6345_out_panel: endpoint@0 {90 anx6345_out_panel: endpoint {
96 reg = <0>;
97 remote-endpoint = <&panel_in_edp>;91 remote-endpoint = <&panel_in_edp>;
98 };92 };
99 };93 };
Documentation/devicetree/bindings/display/panel/leadtek,ltk500hd1829.yaml+2−0
@@ -37,6 +37,8 @@ examples: · 36 unmodified lines
37 dsi@ff450000 {37 dsi@ff450000 {
38 #address-cells = <1>;38 #address-cells = <1>;
39 #size-cells = <0>;39 #size-cells = <0>;
40 reg = <0xff450000 0x1000>;
41
40 panel@0 {42 panel@0 {
41 compatible = "leadtek,ltk500hd1829";43 compatible = "leadtek,ltk500hd1829";
42 reg = <0>;44 reg = <0>;
Documentation/devicetree/bindings/display/panel/xinpeng,xpp055c272.yaml+2−0
@@ -37,6 +37,8 @@ examples: · 36 unmodified lines
37 dsi@ff450000 {37 dsi@ff450000 {
38 #address-cells = <1>;38 #address-cells = <1>;
39 #size-cells = <0>;39 #size-cells = <0>;
40 reg = <0xff450000 0x1000>;
41
40 panel@0 {42 panel@0 {
41 compatible = "xinpeng,xpp055c272";43 compatible = "xinpeng,xpp055c272";
42 reg = <0>;44 reg = <0>;
Documentation/devicetree/bindings/display/simple-framebuffer.yaml+1−5
@@ -174,10 +174,6 @@ examples: · 173 unmodified lines
174 };174 };
175 };175 };
176 176
177 soc@1c00000 {177 lcdc0: lcdc { };
178 lcdc0: lcdc@1c0c000 {
179 compatible = "allwinner,sun4i-a10-lcdc";
180 };
181 };
182 178
183...179...
Documentation/devicetree/bindings/display/tilcdc/tilcdc.txt+1−1
@@ -37,7 +37,7 @@ Optional nodes: · 36 unmodified lines
37 supports a single port with a single endpoint.37 supports a single port with a single endpoint.
38 38
39 - See also Documentation/devicetree/bindings/display/tilcdc/panel.txt and39 - See also Documentation/devicetree/bindings/display/tilcdc/panel.txt and
40 Documentation/devicetree/bindings/display/tilcdc/tfp410.txt for connecting40 Documentation/devicetree/bindings/display/bridge/ti,tfp410.txt for connecting
41 tfp410 DVI encoder or lcd panel to lcdc41 tfp410 DVI encoder or lcd panel to lcdc
42 42
43[1] There is an errata about AM335x color wiring. For 16-bit color mode43[1] There is an errata about AM335x color wiring. For 16-bit color mode
Documentation/devicetree/bindings/dma/ti/k3-udma.yaml+1−13
@@ -143,7 +143,7 @@ examples: · 142 unmodified lines
143 #size-cells = <2>;143 #size-cells = <2>;
144 dma-coherent;144 dma-coherent;
145 dma-ranges;145 dma-ranges;
146 ranges;146 ranges = <0x0 0x30800000 0x0 0x30800000 0x0 0x05000000>;
147 147
148 ti,sci-dev-id = <118>;148 ti,sci-dev-id = <118>;
149 149
@@ -169,16 +169,4 @@ examples: · 19 unmodified lines
169 ti,sci-rm-range-rflow = <0x6>; /* GP RFLOW */169 ti,sci-rm-range-rflow = <0x6>; /* GP RFLOW */
170 };170 };
171 };171 };
172
173 mcasp0: mcasp@02B00000 {
174 dmas = <&main_udmap 0xc400>, <&main_udmap 0x4400>;
175 dma-names = "tx", "rx";
176 };
177
178 crypto: crypto@4E00000 {
179 compatible = "ti,sa2ul-crypto";
180
181 dmas = <&main_udmap 0xc000>, <&main_udmap 0x4000>, <&main_udmap 0x4001>;
182 dma-names = "tx", "rx1", "rx2";
183 };
184 };172 };
Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml+7−7
@@ -84,31 +84,31 @@ examples: · 83 unmodified lines
84 gpu_opp_table: opp_table0 {84 gpu_opp_table: opp_table0 {
85 compatible = "operating-points-v2";85 compatible = "operating-points-v2";
86 86
87 opp@533000000 {87 opp-533000000 {
88 opp-hz = /bits/ 64 <533000000>;88 opp-hz = /bits/ 64 <533000000>;
89 opp-microvolt = <1250000>;89 opp-microvolt = <1250000>;
90 };90 };
91 opp@450000000 {91 opp-450000000 {
92 opp-hz = /bits/ 64 <450000000>;92 opp-hz = /bits/ 64 <450000000>;
93 opp-microvolt = <1150000>;93 opp-microvolt = <1150000>;
94 };94 };
95 opp@400000000 {95 opp-400000000 {
96 opp-hz = /bits/ 64 <400000000>;96 opp-hz = /bits/ 64 <400000000>;
97 opp-microvolt = <1125000>;97 opp-microvolt = <1125000>;
98 };98 };
99 opp@350000000 {99 opp-350000000 {
100 opp-hz = /bits/ 64 <350000000>;100 opp-hz = /bits/ 64 <350000000>;
101 opp-microvolt = <1075000>;101 opp-microvolt = <1075000>;
102 };102 };
103 opp@266000000 {103 opp-266000000 {
104 opp-hz = /bits/ 64 <266000000>;104 opp-hz = /bits/ 64 <266000000>;
105 opp-microvolt = <1025000>;105 opp-microvolt = <1025000>;
106 };106 };
107 opp@160000000 {107 opp-160000000 {
108 opp-hz = /bits/ 64 <160000000>;108 opp-hz = /bits/ 64 <160000000>;
109 opp-microvolt = <925000>;109 opp-microvolt = <925000>;
110 };110 };
111 opp@100000000 {111 opp-100000000 {
112 opp-hz = /bits/ 64 <100000000>;112 opp-hz = /bits/ 64 <100000000>;
113 opp-microvolt = <912500>;113 opp-microvolt = <912500>;
114 };114 };
Documentation/devicetree/bindings/gpu/arm,mali-midgard.yaml+7−7
@@ -138,31 +138,31 @@ examples: · 137 unmodified lines
138 gpu_opp_table: opp_table0 {138 gpu_opp_table: opp_table0 {
139 compatible = "operating-points-v2";139 compatible = "operating-points-v2";
140 140
141 opp@533000000 {141 opp-533000000 {
142 opp-hz = /bits/ 64 <533000000>;142 opp-hz = /bits/ 64 <533000000>;
143 opp-microvolt = <1250000>;143 opp-microvolt = <1250000>;
144 };144 };
145 opp@450000000 {145 opp-450000000 {
146 opp-hz = /bits/ 64 <450000000>;146 opp-hz = /bits/ 64 <450000000>;
147 opp-microvolt = <1150000>;147 opp-microvolt = <1150000>;
148 };148 };
149 opp@400000000 {149 opp-400000000 {
150 opp-hz = /bits/ 64 <400000000>;150 opp-hz = /bits/ 64 <400000000>;
151 opp-microvolt = <1125000>;151 opp-microvolt = <1125000>;
152 };152 };
153 opp@350000000 {153 opp-350000000 {
154 opp-hz = /bits/ 64 <350000000>;154 opp-hz = /bits/ 64 <350000000>;
155 opp-microvolt = <1075000>;155 opp-microvolt = <1075000>;
156 };156 };
157 opp@266000000 {157 opp-266000000 {
158 opp-hz = /bits/ 64 <266000000>;158 opp-hz = /bits/ 64 <266000000>;
159 opp-microvolt = <1025000>;159 opp-microvolt = <1025000>;
160 };160 };
161 opp@160000000 {161 opp-160000000 {
162 opp-hz = /bits/ 64 <160000000>;162 opp-hz = /bits/ 64 <160000000>;
163 opp-microvolt = <925000>;163 opp-microvolt = <925000>;
164 };164 };
165 opp@100000000 {165 opp-100000000 {
166 opp-hz = /bits/ 64 <100000000>;166 opp-hz = /bits/ 64 <100000000>;
167 opp-microvolt = <912500>;167 opp-microvolt = <912500>;
168 };168 };
Documentation/devicetree/bindings/iio/adc/samsung,exynos-adc.yaml+1−1
@@ -123,7 +123,7 @@ examples: · 122 unmodified lines
123 samsung,syscon-phandle = <&pmu_system_controller>;123 samsung,syscon-phandle = <&pmu_system_controller>;
124 124
125 /* NTC thermistor is a hwmon device */125 /* NTC thermistor is a hwmon device */
126 ncp15wb473@0 {126 ncp15wb473 {
127 compatible = "murata,ncp15wb473";127 compatible = "murata,ncp15wb473";
128 pullup-uv = <1800000>;128 pullup-uv = <1800000>;
129 pullup-ohm = <47000>;129 pullup-ohm = <47000>;
Documentation/devicetree/bindings/input/touchscreen/goodix.yaml+1−1
@@ -62,7 +62,7 @@ required: · 61 unmodified lines
62 62
63examples:63examples:
64- |64- |
65 i2c@00000000 {65 i2c {
66 #address-cells = <1>;66 #address-cells = <1>;
67 #size-cells = <0>;67 #size-cells = <0>;
68 gt928@5d {68 gt928@5d {
Documentation/devicetree/bindings/input/twl4030-pwrbutton.txt+1−1
@@ -1,7 +1,7 @@
1Texas Instruments TWL family (twl4030) pwrbutton module1Texas Instruments TWL family (twl4030) pwrbutton module
2 2
3This module is part of the TWL4030. For more details about the whole3This module is part of the TWL4030. For more details about the whole
4chip see Documentation/devicetree/bindings/mfd/twl-familly.txt.4chip see Documentation/devicetree/bindings/mfd/twl-family.txt.
5 5
6This module provides a simple power button event via an Interrupt.6This module provides a simple power button event via an Interrupt.
7 7
Documentation/devicetree/bindings/leds/common.yaml+1−1
@@ -85,7 +85,7 @@ properties: · 84 unmodified lines
85 # LED will act as a back-light, controlled by the framebuffer system85 # LED will act as a back-light, controlled by the framebuffer system
86 - backlight86 - backlight
87 # LED will turn on (but for leds-gpio see "default-state" property in87 # LED will turn on (but for leds-gpio see "default-state" property in
88 # Documentation/devicetree/bindings/leds/leds-gpio.txt)88 # Documentation/devicetree/bindings/leds/leds-gpio.yaml)
89 - default-on89 - default-on
90 # LED "double" flashes at a load average based rate90 # LED "double" flashes at a load average based rate
91 - heartbeat91 - heartbeat
Documentation/devicetree/bindings/leds/register-bit-led.txt+1−1
@@ -5,7 +5,7 @@ where single bits in a certain register can turn on/off a · 4 unmodified lines
5single LED. The register bit LEDs appear as children to the5single LED. The register bit LEDs appear as children to the
6syscon device, with the proper compatible string. For the6syscon device, with the proper compatible string. For the
7syscon bindings see:7syscon bindings see:
8Documentation/devicetree/bindings/mfd/syscon.txt8Documentation/devicetree/bindings/mfd/syscon.yaml
9 9
10Each LED is represented as a sub-node of the syscon device. Each10Each LED is represented as a sub-node of the syscon device. Each
11node's name represents the name of the corresponding LED.11node's name represents the name of the corresponding LED.
Documentation/devicetree/bindings/media/ti,cal.yaml+1−1
@@ -177,7 +177,7 @@ examples: · 176 unmodified lines
177 };177 };
178 };178 };
179 179
180 i2c5: i2c@4807c000 {180 i2c {
181 clock-frequency = <400000>;181 clock-frequency = <400000>;
182 #address-cells = <1>;182 #address-cells = <1>;
183 #size-cells = <0>;183 #size-cells = <0>;
Documentation/devicetree/bindings/memory-controllers/ti/emif.txt+1−1
@@ -32,7 +32,7 @@ Required only for "ti,emif-am3352" and "ti,emif-am4372": · 31 unmodified lines
32- sram : Phandles for generic sram driver nodes,32- sram : Phandles for generic sram driver nodes,
33 first should be type 'protect-exec' for the driver to use to copy33 first should be type 'protect-exec' for the driver to use to copy
34 and run PM functions, second should be regular pool to be used for34 and run PM functions, second should be regular pool to be used for
35 data region for code. See Documentation/devicetree/bindings/sram/sram.txt35 data region for code. See Documentation/devicetree/bindings/sram/sram.yaml
36 for more details.36 for more details.
37 37
38Optional properties:38Optional properties:
Documentation/devicetree/bindings/mfd/max77650.yaml+2−2
@@ -97,14 +97,14 @@ examples: · 96 unmodified lines
97 regulators {97 regulators {
98 compatible = "maxim,max77650-regulator";98 compatible = "maxim,max77650-regulator";
99 99
100 max77650_ldo: regulator@0 {100 max77650_ldo: regulator-ldo {
101 regulator-compatible = "ldo";101 regulator-compatible = "ldo";
102 regulator-name = "max77650-ldo";102 regulator-name = "max77650-ldo";
103 regulator-min-microvolt = <1350000>;103 regulator-min-microvolt = <1350000>;
104 regulator-max-microvolt = <2937500>;104 regulator-max-microvolt = <2937500>;
105 };105 };
106 106
107 max77650_sbb0: regulator@1 {107 max77650_sbb0: regulator-sbb0 {
108 regulator-compatible = "sbb0";108 regulator-compatible = "sbb0";
109 regulator-name = "max77650-sbb0";109 regulator-name = "max77650-sbb0";
110 regulator-min-microvolt = <800000>;110 regulator-min-microvolt = <800000>;
Documentation/devicetree/bindings/mfd/tps65910.txt+2−2
@@ -26,8 +26,8 @@ Required properties: · 25 unmodified lines
26 ldo6, ldo7, ldo826 ldo6, ldo7, ldo8
27 27
28- xxx-supply: Input voltage supply regulator.28- xxx-supply: Input voltage supply regulator.
29 These entries are require if regulators are enabled for a device. Missing of these29 These entries are required if regulators are enabled for a device. Missing these
30 properties can cause the regulator registration fails.30 properties can cause the regulator registration to fail.
31 If some of input supply is powered through battery or always-on supply then31 If some of input supply is powered through battery or always-on supply then
32 also it is require to have these parameters with proper node handle of always32 also it is require to have these parameters with proper node handle of always
33 on power supply.33 on power supply.
Documentation/devicetree/bindings/mfd/twl-family.txtrenamed from Documentation/devicetree/bindings/mfd/twl-familly.txt+0−0

File renamed without changes.

Documentation/devicetree/bindings/mfd/zii,rave-sp.txt+1−1
@@ -20,7 +20,7 @@ RAVE SP consists of the following sub-devices: · 19 unmodified lines
20Device Description20Device Description
21------ -----------21------ -----------
22rave-sp-wdt : Watchdog22rave-sp-wdt : Watchdog
23rave-sp-nvmem : Interface to onborad EEPROM23rave-sp-nvmem : Interface to onboard EEPROM
24rave-sp-backlight : Display backlight24rave-sp-backlight : Display backlight
25rave-sp-hwmon : Interface to onboard hardware sensors25rave-sp-hwmon : Interface to onboard hardware sensors
26rave-sp-leds : Interface to onboard LEDs26rave-sp-leds : Interface to onboard LEDs
Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt+1−1
@@ -26,7 +26,7 @@ For generic IOMMU bindings, see · 25 unmodified lines
26Documentation/devicetree/bindings/iommu/iommu.txt.26Documentation/devicetree/bindings/iommu/iommu.txt.
27 27
28For arm-smmu binding, see:28For arm-smmu binding, see:
29Documentation/devicetree/bindings/iommu/arm,smmu.txt.29Documentation/devicetree/bindings/iommu/arm,smmu.yaml.
30 30
31Required properties:31Required properties:
32 32
Documentation/devicetree/bindings/mmc/mmc-controller.yaml+1−0
@@ -370,6 +370,7 @@ examples: · 369 unmodified lines
370 mmc3: mmc@1c12000 {370 mmc3: mmc@1c12000 {
371 #address-cells = <1>;371 #address-cells = <1>;
372 #size-cells = <0>;372 #size-cells = <0>;
373 reg = <0x1c12000 0x200>;
373 pinctrl-names = "default";374 pinctrl-names = "default";
374 pinctrl-0 = <&mmc3_pins_a>;375 pinctrl-0 = <&mmc3_pins_a>;
375 vmmc-supply = <&reg_vmmc3>;376 vmmc-supply = <&reg_vmmc3>;
Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt+1−1
@@ -27,7 +27,7 @@ Required properties of NAND chips: · 26 unmodified lines
27 - reg: shall contain the native Chip Select ids from 0 to max supported by27 - reg: shall contain the native Chip Select ids from 0 to max supported by
28 the cadence nand flash controller28 the cadence nand flash controller
29 29
30See Documentation/devicetree/bindings/mtd/nand.txt for more details on30See Documentation/devicetree/bindings/mtd/nand-controller.yaml for more details on
31generic bindings.31generic bindings.
32 32
33Example:33Example:
Documentation/devicetree/bindings/net/brcm,bcm7445-switch-v4.0.txt+1−1
@@ -45,7 +45,7 @@ Optional properties: · 44 unmodified lines
45 switch queue45 switch queue
46 46
47- resets: a single phandle and reset identifier pair. See47- resets: a single phandle and reset identifier pair. See
48 Documentation/devicetree/binding/reset/reset.txt for details.48 Documentation/devicetree/bindings/reset/reset.txt for details.
49 49
50- reset-names: If the "reset" property is specified, this property should have50- reset-names: If the "reset" property is specified, this property should have
51 the value "switch" to denote the switch reset line.51 the value "switch" to denote the switch reset line.
Documentation/devicetree/bindings/nvmem/nvmem.yaml+2−0
@@ -76,6 +76,8 @@ examples: · 75 unmodified lines
76 qfprom: eeprom@700000 {76 qfprom: eeprom@700000 {
77 #address-cells = <1>;77 #address-cells = <1>;
78 #size-cells = <1>;78 #size-cells = <1>;
79 reg = <0x00700000 0x100000>;
80
79 wp-gpios = <&gpio1 3 GPIO_ACTIVE_HIGH>;81 wp-gpios = <&gpio1 3 GPIO_ACTIVE_HIGH>;
80 82
81 /* ... */83 /* ... */
Documentation/devicetree/bindings/phy/allwinner,sun4i-a10-usb-phy.yaml+1−1
@@ -86,7 +86,7 @@ examples: · 85 unmodified lines
86 #include <dt-bindings/clock/sun4i-a10-ccu.h>86 #include <dt-bindings/clock/sun4i-a10-ccu.h>
87 #include <dt-bindings/reset/sun4i-a10-ccu.h>87 #include <dt-bindings/reset/sun4i-a10-ccu.h>
88 88
89 usbphy: phy@01c13400 {89 usbphy: phy@1c13400 {
90 #phy-cells = <1>;90 #phy-cells = <1>;
91 compatible = "allwinner,sun4i-a10-usb-phy";91 compatible = "allwinner,sun4i-a10-usb-phy";
92 reg = <0x01c13400 0x10>, <0x01c14800 0x4>, <0x01c1c800 0x4>;92 reg = <0x01c13400 0x10>, <0x01c14800 0x4>, <0x01c1c800 0x4>;
Documentation/devicetree/bindings/pinctrl/aspeed,ast2400-pinctrl.yaml+1−1
@@ -17,7 +17,7 @@ description: |+ · 16 unmodified lines
17 "aspeed,ast2400-scu", "syscon", "simple-mfd"17 "aspeed,ast2400-scu", "syscon", "simple-mfd"
18 18
19 Refer to the the bindings described in19 Refer to the the bindings described in
20 Documentation/devicetree/bindings/mfd/syscon.txt20 Documentation/devicetree/bindings/mfd/syscon.yaml
21 21
22properties:22properties:
23 compatible:23 compatible:
Documentation/devicetree/bindings/pinctrl/aspeed,ast2500-pinctrl.yaml+1−1
@@ -18,7 +18,7 @@ description: |+ · 17 unmodified lines
18 "aspeed,g5-scu", "syscon", "simple-mfd"18 "aspeed,g5-scu", "syscon", "simple-mfd"
19 19
20 Refer to the the bindings described in20 Refer to the the bindings described in
21 Documentation/devicetree/bindings/mfd/syscon.txt21 Documentation/devicetree/bindings/mfd/syscon.yaml
22 22
23properties:23properties:
24 compatible:24 compatible:
Documentation/devicetree/bindings/pinctrl/aspeed,ast2600-pinctrl.yaml+1−1
@@ -17,7 +17,7 @@ description: |+ · 16 unmodified lines
17 "aspeed,ast2600-scu", "syscon", "simple-mfd"17 "aspeed,ast2600-scu", "syscon", "simple-mfd"
18 18
19 Refer to the the bindings described in19 Refer to the the bindings described in
20 Documentation/devicetree/bindings/mfd/syscon.txt20 Documentation/devicetree/bindings/mfd/syscon.yaml
21 21
22properties:22properties:
23 compatible:23 compatible:
Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml+1−1
@@ -248,7 +248,7 @@ examples: · 247 unmodified lines
248 };248 };
249 249
250 //Example 3 pin groups250 //Example 3 pin groups
251 pinctrl@60020000 {251 pinctrl {
252 usart1_pins_a: usart1-0 {252 usart1_pins_a: usart1-0 {
253 pins1 {253 pins1 {
254 pinmux = <STM32_PINMUX('A', 9, AF7)>;254 pinmux = <STM32_PINMUX('A', 9, AF7)>;
Documentation/devicetree/bindings/power/amlogic,meson-ee-pwrc.yaml+1−1
@@ -18,7 +18,7 @@ description: |+ · 17 unmodified lines
18 "amlogic,meson-gx-hhi-sysctrl", "simple-mfd", "syscon"18 "amlogic,meson-gx-hhi-sysctrl", "simple-mfd", "syscon"
19 19
20 Refer to the the bindings described in20 Refer to the the bindings described in
21 Documentation/devicetree/bindings/mfd/syscon.txt21 Documentation/devicetree/bindings/mfd/syscon.yaml
22 22
23properties:23properties:
24 compatible:24 compatible:
Documentation/devicetree/bindings/power/domain-idle-state.txt+0−33
@@ -1,33 +0,0 @@
1PM Domain Idle State Node:
2
3A domain idle state node represents the state parameters that will be used to
4select the state when there are no active components in the domain.
5
6The state node has the following parameters -
7
8- compatible:
9 Usage: Required
10 Value type: <string>
11 Definition: Must be "domain-idle-state".
12
13- entry-latency-us
14 Usage: Required
15 Value type: <prop-encoded-array>
16 Definition: u32 value representing worst case latency in
17 microseconds required to enter the idle state.
18 The exit-latency-us duration may be guaranteed
19 only after entry-latency-us has passed.
20
21- exit-latency-us
22 Usage: Required
23 Value type: <prop-encoded-array>
24 Definition: u32 value representing worst case latency
25 in microseconds required to exit the idle state.
26
27- min-residency-us
28 Usage: Required
29 Value type: <prop-encoded-array>
30 Definition: u32 value representing minimum residency duration
31 in microseconds after which the idle state will yield
32 power benefits after overcoming the overhead in entering
33i the idle state.
Documentation/devicetree/bindings/power/domain-idle-state.yaml+64−0
@@ -0,0 +1,64 @@
1# SPDX-License-Identifier: GPL-2.0
2%YAML 1.2
3---
4$id: http://devicetree.org/schemas/power/domain-idle-state.yaml#
5$schema: http://devicetree.org/meta-schemas/core.yaml#
6
7title: PM Domain Idle States binding description
8
9maintainers:
10 - Ulf Hansson <ulf.hansson@linaro.org>
11
12description:
13 A domain idle state node represents the state parameters that will be used to
14 select the state when there are no active components in the PM domain.
15
16properties:
17 $nodename:
18 const: domain-idle-states
19
20patternProperties:
21 "^(cpu|cluster|domain)-":
22 type: object
23 description:
24 Each state node represents a domain idle state description.
25
26 properties:
27 compatible:
28 const: domain-idle-state
29
30 entry-latency-us:
31 description:
32 The worst case latency in microseconds required to enter the idle
33 state. Note that, the exit-latency-us duration may be guaranteed only
34 after the entry-latency-us has passed.
35
36 exit-latency-us:
37 description:
38 The worst case latency in microseconds required to exit the idle
39 state.
40
41 min-residency-us:
42 description:
43 The minimum residency duration in microseconds after which the idle
44 state will yield power benefits, after overcoming the overhead while
45 entering the idle state.
46
47 required:
48 - compatible
49 - entry-latency-us
50 - exit-latency-us
51 - min-residency-us
52
53examples:
54 - |
55
56 domain-idle-states {
57 domain_retention: domain-retention {
58 compatible = "domain-idle-state";
59 entry-latency-us = <20>;
60 exit-latency-us = <40>;
61 min-residency-us = <80>;
62 };
63 };
64...
Documentation/devicetree/bindings/power/power-domain.yaml+11−13
@@ -25,22 +25,20 @@ description: |+ · 24 unmodified lines
25 25
26properties:26properties:
27 $nodename:27 $nodename:
28 pattern: "^(power-controller|power-domain)(@.*)?$"28 pattern: "^(power-controller|power-domain)([@-].*)?$"
29 29
30 domain-idle-states:30 domain-idle-states:
31 $ref: /schemas/types.yaml#/definitions/phandle-array31 $ref: /schemas/types.yaml#/definitions/phandle-array
32 description:32 description: |
33 A phandle of an idle-state that shall be soaked into a generic domain33 Phandles of idle states that defines the available states for the
34 power state. The idle state definitions are compatible with34 power-domain provider. The idle state definitions are compatible with the
35 domain-idle-state specified in35 domain-idle-state bindings, specified in ./domain-idle-state.yaml.
36 Documentation/devicetree/bindings/power/domain-idle-state.txt36
37 phandles that are not compatible with domain-idle-state will be ignored.37 Note that, the domain-idle-state property reflects the idle states of this
38 The domain-idle-state property reflects the idle state of this PM domain38 PM domain and not the idle states of the devices or sub-domains in the PM
39 and not the idle states of the devices or sub-domains in the PM domain.39 domain. Devices and sub-domains have their own idle states independent of
40 Devices and sub-domains have their own idle-states independent40 the parent domain's idle states. In the absence of this property, the
41 of the parent domain's idle states. In the absence of this property,41 domain would be considered as capable of being powered-on or powered-off.
42 the domain would be considered as capable of being powered-on
43 or powered-off.
44 42
45 operating-points-v2:43 operating-points-v2:
46 $ref: /schemas/types.yaml#/definitions/phandle-array44 $ref: /schemas/types.yaml#/definitions/phandle-array
Documentation/devicetree/bindings/power/power_domain.txt+1−1
@@ -109,4 +109,4 @@ Example: · 108 unmodified lines
109 required-opps = <&domain1_opp_1>;109 required-opps = <&domain1_opp_1>;
110 };110 };
111 111
112[1]. Documentation/devicetree/bindings/power/domain-idle-state.txt112[1]. Documentation/devicetree/bindings/power/domain-idle-state.yaml
Documentation/devicetree/bindings/regulator/regulator.yaml+1−1
@@ -191,7 +191,7 @@ patternProperties: · 190 unmodified lines
191 191
192examples:192examples:
193 - |193 - |
194 xyzreg: regulator@0 {194 xyzreg: regulator {
195 regulator-min-microvolt = <1000000>;195 regulator-min-microvolt = <1000000>;
196 regulator-max-microvolt = <2500000>;196 regulator-max-microvolt = <2500000>;
197 regulator-always-on;197 regulator-always-on;
Documentation/devicetree/bindings/reset/st,stm32mp1-rcc.txt+1−1
@@ -3,4 +3,4 @@ STMicroelectronics STM32MP1 Peripheral Reset Controller · 2 unmodified lines
3 3
4The RCC IP is both a reset and a clock controller.4The RCC IP is both a reset and a clock controller.
5 5
6Please see Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.txt6Please see Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml
Documentation/devicetree/bindings/sound/st,stm32-sai.txt+1−1
@@ -36,7 +36,7 @@ SAI subnodes required properties: · 35 unmodified lines
36 - clock-names: Must contain "sai_ck".36 - clock-names: Must contain "sai_ck".
37 Must also contain "MCLK", if SAI shares a master clock,37 Must also contain "MCLK", if SAI shares a master clock,
38 with a SAI set as MCLK clock provider.38 with a SAI set as MCLK clock provider.
39 - dmas: see Documentation/devicetree/bindings/dma/stm32-dma.txt39 - dmas: see Documentation/devicetree/bindings/dma/st,stm32-dma.yaml
40 - dma-names: identifier string for each DMA request line40 - dma-names: identifier string for each DMA request line
41 "tx": if sai sub-block is configured as playback DAI41 "tx": if sai sub-block is configured as playback DAI
42 "rx": if sai sub-block is configured as capture DAI42 "rx": if sai sub-block is configured as capture DAI
Documentation/devicetree/bindings/sound/st,stm32-spdifrx.txt+1−1
@@ -10,7 +10,7 @@ Required properties: · 9 unmodified lines
10 - clock-names: must contain "kclk"10 - clock-names: must contain "kclk"
11 - interrupts: cpu DAI interrupt line11 - interrupts: cpu DAI interrupt line
12 - dmas: DMA specifiers for audio data DMA and iec control flow DMA12 - dmas: DMA specifiers for audio data DMA and iec control flow DMA
13 See STM32 DMA bindings, Documentation/devicetree/bindings/dma/stm32-dma.txt13 See STM32 DMA bindings, Documentation/devicetree/bindings/dma/st,stm32-dma.yaml
14 - dma-names: two dmas have to be defined, "rx" and "rx-ctrl"14 - dma-names: two dmas have to be defined, "rx" and "rx-ctrl"
15 15
16Optional properties:16Optional properties:
Documentation/devicetree/bindings/spi/st,stm32-spi.yaml+1−1
@@ -49,7 +49,7 @@ properties: · 48 unmodified lines
49 dmas:49 dmas:
50 description: |50 description: |
51 DMA specifiers for tx and rx dma. DMA fifo mode must be used. See51 DMA specifiers for tx and rx dma. DMA fifo mode must be used. See
52 the STM32 DMA bindings Documentation/devicetree/bindings/dma/stm32-dma.txt.52 the STM32 DMA bindings Documentation/devicetree/bindings/dma/st,stm32-dma.yaml.
53 items:53 items:
54 - description: rx DMA channel54 - description: rx DMA channel
55 - description: tx DMA channel55 - description: tx DMA channel
Documentation/devicetree/bindings/sram/allwinner,sun4i-a10-system-control.yaml+1−1
@@ -125,7 +125,7 @@ examples: · 124 unmodified lines
125 #size-cells = <1>;125 #size-cells = <1>;
126 ranges;126 ranges;
127 127
128 sram_a: sram@00000000 {128 sram_a: sram@0 {
129 compatible = "mmio-sram";129 compatible = "mmio-sram";
130 reg = <0x00000000 0xc000>;130 reg = <0x00000000 0xc000>;
131 #address-cells = <1>;131 #address-cells = <1>;
Documentation/devicetree/bindings/thermal/brcm,avs-ro-thermal.yaml+1−1
@@ -17,7 +17,7 @@ description: |+ · 16 unmodified lines
17 "brcm,bcm2711-avs-monitor", "syscon", "simple-mfd"17 "brcm,bcm2711-avs-monitor", "syscon", "simple-mfd"
18 18
19 Refer to the the bindings described in19 Refer to the the bindings described in
20 Documentation/devicetree/bindings/mfd/syscon.txt20 Documentation/devicetree/bindings/mfd/syscon.yaml
21 21
22properties:22properties:
23 compatible:23 compatible:
Documentation/devicetree/bindings/timer/allwinner,sun4i-a10-timer.yaml+1−1
@@ -87,7 +87,7 @@ additionalProperties: false · 86 unmodified lines
87 87
88examples:88examples:
89 - |89 - |
90 timer {90 timer@1c20c00 {
91 compatible = "allwinner,sun4i-a10-timer";91 compatible = "allwinner,sun4i-a10-timer";
92 reg = <0x01c20c00 0x400>;92 reg = <0x01c20c00 0x400>;
93 interrupts = <22>,93 interrupts = <22>,
MAINTAINERS+7−8
@@ -693,7 +693,7 @@ ALLWINNER CPUFREQ DRIVER · 692 unmodified lines
693M: Yangtao Li <tiny.windzz@gmail.com>693M: Yangtao Li <tiny.windzz@gmail.com>
694L: linux-pm@vger.kernel.org694L: linux-pm@vger.kernel.org
695S: Maintained695S: Maintained
696F: Documentation/devicetree/bindings/opp/sun50i-nvmem-cpufreq.txt696F: Documentation/devicetree/bindings/opp/allwinner,sun50i-h6-operating-points.yaml
697F: drivers/cpufreq/sun50i-cpufreq-nvmem.c697F: drivers/cpufreq/sun50i-cpufreq-nvmem.c
698 698
699ALLWINNER CRYPTO DRIVERS699ALLWINNER CRYPTO DRIVERS
@@ -4017,7 +4017,7 @@ M: Cheng-Yi Chiang <cychiang@chromium.org> · 3317 unmodified lines
4017S: Maintained4017S: Maintained
4018R: Enric Balletbo i Serra <enric.balletbo@collabora.com>4018R: Enric Balletbo i Serra <enric.balletbo@collabora.com>
4019R: Guenter Roeck <groeck@chromium.org>4019R: Guenter Roeck <groeck@chromium.org>
4020F: Documentation/devicetree/bindings/sound/google,cros-ec-codec.txt4020F: Documentation/devicetree/bindings/sound/google,cros-ec-codec.yaml
4021F: sound/soc/codecs/cros_ec_codec.*4021F: sound/soc/codecs/cros_ec_codec.*
4022 4022
4023CIRRUS LOGIC AUDIO CODEC DRIVERS4023CIRRUS LOGIC AUDIO CODEC DRIVERS
@@ -4475,7 +4475,7 @@ L: linux-media@vger.kernel.org · 451 unmodified lines
4475T: git git://linuxtv.org/media_tree.git4475T: git git://linuxtv.org/media_tree.git
4476S: Maintained4476S: Maintained
4477F: drivers/media/platform/sunxi/sun6i-csi/4477F: drivers/media/platform/sunxi/sun6i-csi/
4478F: Documentation/devicetree/bindings/media/sun6i-csi.txt4478F: Documentation/devicetree/bindings/media/allwinner,sun6i-a31-csi.yaml
4479 4479
4480CW1200 WLAN driver4480CW1200 WLAN driver
4481M: Solomon Peachy <pizza@shaftnet.org>4481M: Solomon Peachy <pizza@shaftnet.org>
@@ -5668,7 +5668,7 @@ L: dri-devel@lists.freedesktop.org · 1186 unmodified lines
5668T: git git://anongit.freedesktop.org/drm/drm-misc5668T: git git://anongit.freedesktop.org/drm/drm-misc
5669S: Maintained5669S: Maintained
5670F: drivers/gpu/drm/stm5670F: drivers/gpu/drm/stm
5671F: Documentation/devicetree/bindings/display/st,stm32-ltdc.txt5671F: Documentation/devicetree/bindings/display/st,stm32-ltdc.yaml
5672 5672
5673DRM DRIVERS FOR TI LCDC5673DRM DRIVERS FOR TI LCDC
5674M: Jyri Sarha <jsarha@ti.com>5674M: Jyri Sarha <jsarha@ti.com>
@@ -10164,7 +10164,7 @@ MAXBOTIX ULTRASONIC RANGER IIO DRIVER · 4489 unmodified lines
10164M: Andreas Klinger <ak@it-klinger.de>10164M: Andreas Klinger <ak@it-klinger.de>
10165L: linux-iio@vger.kernel.org10165L: linux-iio@vger.kernel.org
10166S: Maintained10166S: Maintained
10167F: Documentation/devicetree/bindings/iio/proximity/maxbotix,mb1232.txt10167F: Documentation/devicetree/bindings/iio/proximity/maxbotix,mb1232.yaml
10168F: drivers/iio/proximity/mb1232.c10168F: drivers/iio/proximity/mb1232.c
10169 10169
10170MAXIM MAX77650 PMIC MFD DRIVER10170MAXIM MAX77650 PMIC MFD DRIVER
@@ -10467,7 +10467,7 @@ M: Hugues Fruchet <hugues.fruchet@st.com> · 296 unmodified lines
10467L: linux-media@vger.kernel.org10467L: linux-media@vger.kernel.org
10468T: git git://linuxtv.org/media_tree.git10468T: git git://linuxtv.org/media_tree.git
10469S: Supported10469S: Supported
10470F: Documentation/devicetree/bindings/media/st,stm32-dcmi.txt10470F: Documentation/devicetree/bindings/media/st,stm32-dcmi.yaml
10471F: drivers/media/platform/stm32/stm32-dcmi.c10471F: drivers/media/platform/stm32/stm32-dcmi.c
10472 10472
10473MEDIA DRIVERS FOR NVIDIA TEGRA - VDE10473MEDIA DRIVERS FOR NVIDIA TEGRA - VDE
@@ -12952,7 +12952,6 @@ M: Robert Richter <rrichter@marvell.com> · 2478 unmodified lines
12952L: linux-pci@vger.kernel.org12952L: linux-pci@vger.kernel.org
12953L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)12953L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
12954S: Supported12954S: Supported
12955F: Documentation/devicetree/bindings/pci/pci-thunder-*
12956F: drivers/pci/controller/pci-thunder-*12955F: drivers/pci/controller/pci-thunder-*
12957 12956
12958PCIE DRIVER FOR HISILICON12957PCIE DRIVER FOR HISILICON
@@ -15922,7 +15921,7 @@ F: drivers/*/stm32-*timer* · 2963 unmodified lines
15922F: drivers/pwm/pwm-stm32*15921F: drivers/pwm/pwm-stm32*
15923F: include/linux/*/stm32-*tim*15922F: include/linux/*/stm32-*tim*
15924F: Documentation/ABI/testing/*timer-stm3215923F: Documentation/ABI/testing/*timer-stm32
15925F: Documentation/devicetree/bindings/*/stm32-*timer*15924F: Documentation/devicetree/bindings/*/*stm32-*timer*
15926F: Documentation/devicetree/bindings/pwm/pwm-stm32*15925F: Documentation/devicetree/bindings/pwm/pwm-stm32*
15927 15926
15928STMMAC ETHERNET DRIVER15927STMMAC ETHERNET DRIVER
drivers/staging/wfx/Documentation/devicetree/bindings/net/wireless/siliabs,wfx.txt+1−1
@@ -93,5 +93,5 @@ Some properties are recognized either by SPI and SDIO versions: · 92 unmodified lines
93 Must contains 64 hexadecimal digits. Not supported in current version.93 Must contains 64 hexadecimal digits. Not supported in current version.
94 94
95WFx driver also supports `mac-address` and `local-mac-address` as described in95WFx driver also supports `mac-address` and `local-mac-address` as described in
96Documentation/devicetree/binding/net/ethernet.txt96Documentation/devicetree/bindings/net/ethernet.txt
97 97

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t