redonkable
/
alistair23-linux
1
0
Fork 0
Code Releases Activity

Devicetree fixes for v5.6, take 3: 

- 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
 -----BEGIN PGP SIGNATURE-----
 
 iQJEBAABCgAuFiEEktVUI4SxYhzZyEuo+vtdtY28YcMFAl5iwicQHHJvYmhAa2Vy
 bmVsLm9yZwAKCRD6+121jbxhwxZQD/0VmRBeLZaCg1jiTfj2a+/AbR+x6sGh1izC
 yKI/GRRpVDuyYKN4vNZrY/Z3O5wNwbxZ4mRot/R1EL0on0WPKoLTbioyFFAO3kk0
 7ar6lQCKJHikAz7olT89D0vMD86KGCuUIa0Cju31SCRwdASRtgm36q7ozvs7kt9T
 jkTHfH121sLrSDQCHHq1NPBct6tL6ldtfbClqNSs4HsR/9Bzvnd5Sd3hsjLcotnO
 WpXezH5smBssguJJs0kHySg9gis2DCWnRkejb+7fGC7b8N/vTZA2EWierD0cvpy6
 45SRfRtUeCb8OuTn2V8J8CaPmYTmwUvxrSLR/l3vyB+BvxLULsAMFH9gE5AcgHVY
 eQAj2l8d+Q+bFSUaV3sKPhV3xquBTi6d26pu2uZDjK6MmeLIi3mkOW1bonD5xWbz
 o7KB67g36ENwleou01AbK/bs211hSSHfqKe1pCWIKq9t7xJAkBklSfymr3kAgj9/
 1mwnzwvm2dr8MWH8CNYmNcNb2NAgh2mSgS3yW6WjJcEOUeran+/kn7Ivs/fpDlxF
 JUyYD+ZGQxccYn1c+urrMbzG16HjtqyV6UWUHGJxA2YGs15kSLRvEEIPRbxIsARs
 YPymRSFchmggyb+CLr8XH5XxDDaHm/3ZTsqA3PgFuQopX7OdCmcb7CGGNCmvzhxk
 NC5jllsiLw==
 =sbhb
 -----END PGP SIGNATURE-----

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
alistair/sensors
Linus Torvalds 2020-03-06 16:11:34 -06:00
parent 2f501bb180 d2334a91a3
commit bdf1ea7ca8
59 changed files with 169 additions and 163 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/devicetree/bindings/arm/arm,scmi.txt
View File

@ -102,7 +102,7 @@ Required sub-node properties:
[1] Documentation/devicetree/bindings/clock/clock-bindings.txt [1] Documentation/devicetree/bindings/clock/clock-bindings.txt
[2] Documentation/devicetree/bindings/power/power-domain.yaml [2] Documentation/devicetree/bindings/power/power-domain.yaml
[3] Documentation/devicetree/bindings/thermal/thermal.txt [3] Documentation/devicetree/bindings/thermal/thermal.txt
[4] Documentation/devicetree/bindings/sram/sram.txt [4] Documentation/devicetree/bindings/sram/sram.yaml
[5] Documentation/devicetree/bindings/reset/reset.txt [5] Documentation/devicetree/bindings/reset/reset.txt
Example: Example:

2
Documentation/devicetree/bindings/arm/arm,scpi.txt
View File

@ -109,7 +109,7 @@ Required properties:
[0] http://infocenter.arm.com/help/topic/com.arm.doc.dui0922b/index.html [0] http://infocenter.arm.com/help/topic/com.arm.doc.dui0922b/index.html
[1] Documentation/devicetree/bindings/clock/clock-bindings.txt [1] Documentation/devicetree/bindings/clock/clock-bindings.txt
[2] Documentation/devicetree/bindings/thermal/thermal.txt [2] Documentation/devicetree/bindings/thermal/thermal.txt
[3] Documentation/devicetree/bindings/sram/sram.txt [3] Documentation/devicetree/bindings/sram/sram.yaml
[4] Documentation/devicetree/bindings/power/power-domain.yaml [4] Documentation/devicetree/bindings/power/power-domain.yaml
Example: Example:

2
Documentation/devicetree/bindings/arm/bcm/brcm,bcm63138.txt
View File

@ -62,7 +62,7 @@ Timer node:
Syscon reboot node: Syscon reboot node:
See Documentation/devicetree/bindings/power/reset/syscon-reboot.txt for the See Documentation/devicetree/bindings/power/reset/syscon-reboot.yaml for the
detailed list of properties, the two values defined below are specific to the detailed list of properties, the two values defined below are specific to the
BCM6328-style timer: BCM6328-style timer:

2
Documentation/devicetree/bindings/arm/cpus.yaml
View File

@ -216,7 +216,7 @@ properties:
$ref: '/schemas/types.yaml#/definitions/phandle-array' $ref: '/schemas/types.yaml#/definitions/phandle-array'
description: | description: |
List of phandles to idle state nodes supported List of phandles to idle state nodes supported
by this cpu (see ./idle-states.txt). by this cpu (see ./idle-states.yaml).
capacity-dmips-mhz: capacity-dmips-mhz:
$ref: '/schemas/types.yaml#/definitions/uint32' $ref: '/schemas/types.yaml#/definitions/uint32'

2
Documentation/devicetree/bindings/arm/fsl.yaml
View File

@ -160,7 +160,7 @@ properties:
items: items:
- enum: - enum:
- armadeus,imx6dl-apf6 # APF6 (Solo) SoM - armadeus,imx6dl-apf6 # APF6 (Solo) SoM
- armadeus,imx6dl-apf6dldev # APF6 (Solo) SoM on APF6Dev board - armadeus,imx6dl-apf6dev # APF6 (Solo) SoM on APF6Dev board
- eckelmann,imx6dl-ci4x10 - eckelmann,imx6dl-ci4x10
- emtrion,emcon-mx6 # emCON-MX6S or emCON-MX6DL SoM - emtrion,emcon-mx6 # emCON-MX6S or emCON-MX6DL SoM
- emtrion,emcon-mx6-avari # emCON-MX6S or emCON-MX6DL SoM on Avari Base - emtrion,emcon-mx6-avari # emCON-MX6S or emCON-MX6DL SoM on Avari Base

2
Documentation/devicetree/bindings/arm/hisilicon/hi3519-sysctrl.txt
View File

@ -1,7 +1,7 @@
* Hisilicon Hi3519 System Controller Block * Hisilicon Hi3519 System Controller Block
This bindings use the following binding: This bindings use the following binding:
Documentation/devicetree/bindings/mfd/syscon.txt Documentation/devicetree/bindings/mfd/syscon.yaml
Required properties: Required properties:
- compatible: "hisilicon,hi3519-sysctrl". - compatible: "hisilicon,hi3519-sysctrl".

2
Documentation/devicetree/bindings/arm/msm/qcom,idle-state.txt
View File

@ -81,4 +81,4 @@ Example:
}; };
}; };
[1]. Documentation/devicetree/bindings/arm/idle-states.txt [1]. Documentation/devicetree/bindings/arm/idle-states.yaml

2
Documentation/devicetree/bindings/arm/omap/mpu.txt
View File

@ -17,7 +17,7 @@ am335x and am437x only:
- pm-sram: Phandles to ocmcram nodes to be used for power management. - pm-sram: Phandles to ocmcram nodes to be used for power management.
First should be type 'protect-exec' for the driver to use to copy First should be type 'protect-exec' for the driver to use to copy
and run PM functions, second should be regular pool to be used for and run PM functions, second should be regular pool to be used for
data region for code. See Documentation/devicetree/bindings/sram/sram.txt data region for code. See Documentation/devicetree/bindings/sram/sram.yaml
for more details. for more details.
Examples: Examples:

36
Documentation/devicetree/bindings/arm/psci.yaml
View File

@ -100,13 +100,14 @@ properties:
bindings in [1]) must specify this property. bindings in [1]) must specify this property.
[1] Kernel documentation - ARM idle states bindings [1] Kernel documentation - ARM idle states bindings
Documentation/devicetree/bindings/arm/idle-states.txt Documentation/devicetree/bindings/arm/idle-states.yaml
"#power-domain-cells":
description:
The number of cells in a PM domain specifier as per binding in [3].
Must be 0 as to represent a single PM domain.
patternProperties:
"^power-domain-":
allOf:
- $ref: "../power/power-domain.yaml#"
type: object
description: |
ARM systems can have multiple cores, sometimes in an hierarchical ARM systems can have multiple cores, sometimes in an hierarchical
arrangement. This often, but not always, maps directly to the processor arrangement. This often, but not always, maps directly to the processor
power topology of the system. Individual nodes in a topology have their power topology of the system. Individual nodes in a topology have their
@ -122,14 +123,8 @@ properties:
helps to implement support for OSI mode and OS implementations may choose helps to implement support for OSI mode and OS implementations may choose
to mandate it. to mandate it.
[3] Documentation/devicetree/bindings/power/power_domain.txt [3] Documentation/devicetree/bindings/power/power-domain.yaml
[4] Documentation/devicetree/bindings/power/domain-idle-state.txt [4] Documentation/devicetree/bindings/power/domain-idle-state.yaml
power-domains:
$ref: '/schemas/types.yaml#/definitions/phandle-array'
description:
List of phandles and PM domain specifiers, as defined by bindings of the
PM domain provider.
required: required:
- compatible - compatible
@ -199,7 +194,7 @@ examples:
CPU0: cpu@0 { CPU0: cpu@0 {
device_type = "cpu"; device_type = "cpu";
compatible = "arm,cortex-a53", "arm,armv8"; compatible = "arm,cortex-a53";
reg = <0x0>; reg = <0x0>;
enable-method = "psci"; enable-method = "psci";
power-domains = <&CPU_PD0>; power-domains = <&CPU_PD0>;
@ -208,7 +203,7 @@ examples:
CPU1: cpu@1 { CPU1: cpu@1 {
device_type = "cpu"; device_type = "cpu";
compatible = "arm,cortex-a57", "arm,armv8"; compatible = "arm,cortex-a53";
reg = <0x100>; reg = <0x100>;
enable-method = "psci"; enable-method = "psci";
power-domains = <&CPU_PD1>; power-domains = <&CPU_PD1>;
@ -224,6 +219,9 @@ examples:
exit-latency-us = <10>; exit-latency-us = <10>;
min-residency-us = <100>; min-residency-us = <100>;
}; };
};
domain-idle-states {
CLUSTER_RET: cluster-retention { CLUSTER_RET: cluster-retention {
compatible = "domain-idle-state"; compatible = "domain-idle-state";
@ -247,19 +245,19 @@ examples:
compatible = "arm,psci-1.0"; compatible = "arm,psci-1.0";
method = "smc"; method = "smc";
CPU_PD0: cpu-pd0 { CPU_PD0: power-domain-cpu0 {
#power-domain-cells = <0>; #power-domain-cells = <0>;
domain-idle-states = <&CPU_PWRDN>; domain-idle-states = <&CPU_PWRDN>;
power-domains = <&CLUSTER_PD>; power-domains = <&CLUSTER_PD>;
}; };
CPU_PD1: cpu-pd1 { CPU_PD1: power-domain-cpu1 {
#power-domain-cells = <0>; #power-domain-cells = <0>;
domain-idle-states = <&CPU_PWRDN>; domain-idle-states = <&CPU_PWRDN>;
power-domains = <&CLUSTER_PD>; power-domains = <&CLUSTER_PD>;
}; };
CLUSTER_PD: cluster-pd { CLUSTER_PD: power-domain-cluster {
#power-domain-cells = <0>; #power-domain-cells = <0>;
domain-idle-states = <&CLUSTER_RET>, <&CLUSTER_PWRDN>; domain-idle-states = <&CLUSTER_RET>, <&CLUSTER_PWRDN>;
}; };

2
Documentation/devicetree/bindings/arm/stm32/st,mlahb.yaml
View File

@ -52,7 +52,7 @@ required:
examples: examples:
- | - |
mlahb: ahb { mlahb: ahb@38000000 {
compatible = "st,mlahb", "simple-bus"; compatible = "st,mlahb", "simple-bus";
#address-cells = <1>; #address-cells = <1>;
#size-cells = <1>; #size-cells = <1>;

1
Documentation/devicetree/bindings/bus/allwinner,sun8i-a23-rsb.yaml
View File

@ -70,7 +70,6 @@ examples:
#size-cells = <0>; #size-cells = <0>;
pmic@3e3 { pmic@3e3 {
compatible = "...";
reg = <0x3e3>; reg = <0x3e3>;
/* ... */ /* ... */

2
Documentation/devicetree/bindings/clock/allwinner,sun4i-a10-osc-clk.yaml
View File

@ -40,7 +40,7 @@ additionalProperties: false
examples: examples:
- | - |
osc24M: clk@01c20050 { osc24M: clk@1c20050 {
#clock-cells = <0>; #clock-cells = <0>;
compatible = "allwinner,sun4i-a10-osc-clk"; compatible = "allwinner,sun4i-a10-osc-clk";
reg = <0x01c20050 0x4>; reg = <0x01c20050 0x4>;

2
Documentation/devicetree/bindings/clock/allwinner,sun9i-a80-gt-clk.yaml
View File

@ -41,7 +41,7 @@ additionalProperties: false
examples: examples:
- | - |
clk@0600005c { clk@600005c {
#clock-cells = <0>; #clock-cells = <0>;
compatible = "allwinner,sun9i-a80-gt-clk"; compatible = "allwinner,sun9i-a80-gt-clk";
reg = <0x0600005c 0x4>; reg = <0x0600005c 0x4>;

2
Documentation/devicetree/bindings/clock/qcom,gcc-apq8064.yaml
View File

@ -42,7 +42,7 @@ properties:
be part of GCC and hence the TSENS properties can also be part be part of GCC and hence the TSENS properties can also be part
of the GCC/clock-controller node. of the GCC/clock-controller node.
For more details on the TSENS properties please refer For more details on the TSENS properties please refer
Documentation/devicetree/bindings/thermal/qcom-tsens.txt Documentation/devicetree/bindings/thermal/qcom-tsens.yaml
nvmem-cell-names: nvmem-cell-names:
minItems: 1 minItems: 1

6
Documentation/devicetree/bindings/display/allwinner,sun4i-a10-tv-encoder.yaml
View File

@ -49,11 +49,7 @@ examples:
resets = <&tcon_ch0_clk 0>; resets = <&tcon_ch0_clk 0>;
port { port {
#address-cells = <1>; tve0_in_tcon0: endpoint {
#size-cells = <0>;
tve0_in_tcon0: endpoint@0 {
reg = <0>;
remote-endpoint = <&tcon0_out_tve0>; remote-endpoint = <&tcon0_out_tve0>;
}; };
}; };

10
Documentation/devicetree/bindings/display/bridge/anx6345.yaml
View File

@ -79,21 +79,15 @@ examples:
#size-cells = <0>; #size-cells = <0>;
anx6345_in: port@0 { anx6345_in: port@0 {
#address-cells = <1>;
#size-cells = <0>;
reg = <0>; reg = <0>;
anx6345_in_tcon0: endpoint@0 { anx6345_in_tcon0: endpoint {
reg = <0>;
remote-endpoint = <&tcon0_out_anx6345>; remote-endpoint = <&tcon0_out_anx6345>;
}; };
}; };
anx6345_out: port@1 { anx6345_out: port@1 {
#address-cells = <1>;
#size-cells = <0>;
reg = <1>; reg = <1>;
anx6345_out_panel: endpoint@0 { anx6345_out_panel: endpoint {
reg = <0>;
remote-endpoint = <&panel_in_edp>; remote-endpoint = <&panel_in_edp>;
}; };
}; };

2
Documentation/devicetree/bindings/display/panel/leadtek,ltk500hd1829.yaml
View File

@ -37,6 +37,8 @@ examples:
dsi@ff450000 { dsi@ff450000 {
#address-cells = <1>; #address-cells = <1>;
#size-cells = <0>; #size-cells = <0>;
reg = <0xff450000 0x1000>;
panel@0 { panel@0 {
compatible = "leadtek,ltk500hd1829"; compatible = "leadtek,ltk500hd1829";
reg = <0>; reg = <0>;

2
Documentation/devicetree/bindings/display/panel/xinpeng,xpp055c272.yaml
View File

@ -37,6 +37,8 @@ examples:
dsi@ff450000 { dsi@ff450000 {
#address-cells = <1>; #address-cells = <1>;
#size-cells = <0>; #size-cells = <0>;
reg = <0xff450000 0x1000>;
panel@0 { panel@0 {
compatible = "xinpeng,xpp055c272"; compatible = "xinpeng,xpp055c272";
reg = <0>; reg = <0>;

6
Documentation/devicetree/bindings/display/simple-framebuffer.yaml
View File

@ -174,10 +174,6 @@ examples:
}; };
}; };
soc@1c00000 { lcdc0: lcdc { };
lcdc0: lcdc@1c0c000 {
compatible = "allwinner,sun4i-a10-lcdc";
};
};
... ...

2
Documentation/devicetree/bindings/display/tilcdc/tilcdc.txt
View File

@ -37,7 +37,7 @@ Optional nodes:
supports a single port with a single endpoint. supports a single port with a single endpoint.
- See also Documentation/devicetree/bindings/display/tilcdc/panel.txt and - See also Documentation/devicetree/bindings/display/tilcdc/panel.txt and
Documentation/devicetree/bindings/display/tilcdc/tfp410.txt for connecting Documentation/devicetree/bindings/display/bridge/ti,tfp410.txt for connecting
tfp410 DVI encoder or lcd panel to lcdc tfp410 DVI encoder or lcd panel to lcdc
[1] There is an errata about AM335x color wiring. For 16-bit color mode [1] There is an errata about AM335x color wiring. For 16-bit color mode

14
Documentation/devicetree/bindings/dma/ti/k3-udma.yaml
View File

@ -143,7 +143,7 @@ examples:
#size-cells = <2>; #size-cells = <2>;
dma-coherent; dma-coherent;
dma-ranges; dma-ranges;
ranges; ranges = <0x0 0x30800000 0x0 0x30800000 0x0 0x05000000>;
ti,sci-dev-id = <118>; ti,sci-dev-id = <118>;
@ -169,16 +169,4 @@ examples:
ti,sci-rm-range-rflow = <0x6>; /* GP RFLOW */ ti,sci-rm-range-rflow = <0x6>; /* GP RFLOW */
}; };
}; };
mcasp0: mcasp@02B00000 {
dmas = <&main_udmap 0xc400>, <&main_udmap 0x4400>;
dma-names = "tx", "rx";
};
crypto: crypto@4E00000 {
compatible = "ti,sa2ul-crypto";
dmas = <&main_udmap 0xc000>, <&main_udmap 0x4000>, <&main_udmap 0x4001>;
dma-names = "tx", "rx1", "rx2";
};
}; };

14
Documentation/devicetree/bindings/gpu/arm,mali-bifrost.yaml
View File

@ -84,31 +84,31 @@ examples:
gpu_opp_table: opp_table0 { gpu_opp_table: opp_table0 {
compatible = "operating-points-v2"; compatible = "operating-points-v2";
opp@533000000 { opp-533000000 {
opp-hz = /bits/ 64 <533000000>; opp-hz = /bits/ 64 <533000000>;
opp-microvolt = <1250000>; opp-microvolt = <1250000>;
}; };
opp@450000000 { opp-450000000 {
opp-hz = /bits/ 64 <450000000>; opp-hz = /bits/ 64 <450000000>;
opp-microvolt = <1150000>; opp-microvolt = <1150000>;
}; };
opp@400000000 { opp-400000000 {
opp-hz = /bits/ 64 <400000000>; opp-hz = /bits/ 64 <400000000>;
opp-microvolt = <1125000>; opp-microvolt = <1125000>;
}; };
opp@350000000 { opp-350000000 {
opp-hz = /bits/ 64 <350000000>; opp-hz = /bits/ 64 <350000000>;
opp-microvolt = <1075000>; opp-microvolt = <1075000>;
}; };
opp@266000000 { opp-266000000 {
opp-hz = /bits/ 64 <266000000>; opp-hz = /bits/ 64 <266000000>;
opp-microvolt = <1025000>; opp-microvolt = <1025000>;
}; };
opp@160000000 { opp-160000000 {
opp-hz = /bits/ 64 <160000000>; opp-hz = /bits/ 64 <160000000>;
opp-microvolt = <925000>; opp-microvolt = <925000>;
}; };
opp@100000000 { opp-100000000 {
opp-hz = /bits/ 64 <100000000>; opp-hz = /bits/ 64 <100000000>;
opp-microvolt = <912500>; opp-microvolt = <912500>;
}; };

14
Documentation/devicetree/bindings/gpu/arm,mali-midgard.yaml
View File

@ -138,31 +138,31 @@ examples:
gpu_opp_table: opp_table0 { gpu_opp_table: opp_table0 {
compatible = "operating-points-v2"; compatible = "operating-points-v2";
opp@533000000 { opp-533000000 {
opp-hz = /bits/ 64 <533000000>; opp-hz = /bits/ 64 <533000000>;
opp-microvolt = <1250000>; opp-microvolt = <1250000>;
}; };
opp@450000000 { opp-450000000 {
opp-hz = /bits/ 64 <450000000>; opp-hz = /bits/ 64 <450000000>;
opp-microvolt = <1150000>; opp-microvolt = <1150000>;
}; };
opp@400000000 { opp-400000000 {
opp-hz = /bits/ 64 <400000000>; opp-hz = /bits/ 64 <400000000>;
opp-microvolt = <1125000>; opp-microvolt = <1125000>;
}; };
opp@350000000 { opp-350000000 {
opp-hz = /bits/ 64 <350000000>; opp-hz = /bits/ 64 <350000000>;
opp-microvolt = <1075000>; opp-microvolt = <1075000>;
}; };
opp@266000000 { opp-266000000 {
opp-hz = /bits/ 64 <266000000>; opp-hz = /bits/ 64 <266000000>;
opp-microvolt = <1025000>; opp-microvolt = <1025000>;
}; };
opp@160000000 { opp-160000000 {
opp-hz = /bits/ 64 <160000000>; opp-hz = /bits/ 64 <160000000>;
opp-microvolt = <925000>; opp-microvolt = <925000>;
}; };
opp@100000000 { opp-100000000 {
opp-hz = /bits/ 64 <100000000>; opp-hz = /bits/ 64 <100000000>;
opp-microvolt = <912500>; opp-microvolt = <912500>;
}; };

2
Documentation/devicetree/bindings/iio/adc/samsung,exynos-adc.yaml
View File

@ -123,7 +123,7 @@ examples:
samsung,syscon-phandle = <&pmu_system_controller>; samsung,syscon-phandle = <&pmu_system_controller>;
/* NTC thermistor is a hwmon device */ /* NTC thermistor is a hwmon device */
ncp15wb473@0 { ncp15wb473 {
compatible = "murata,ncp15wb473"; compatible = "murata,ncp15wb473";
pullup-uv = <1800000>; pullup-uv = <1800000>;
pullup-ohm = <47000>; pullup-ohm = <47000>;

2
Documentation/devicetree/bindings/input/touchscreen/goodix.yaml
View File

@ -62,7 +62,7 @@ required:
examples: examples:
- | - |
i2c@00000000 { i2c {
#address-cells = <1>; #address-cells = <1>;
#size-cells = <0>; #size-cells = <0>;
gt928@5d { gt928@5d {

2
Documentation/devicetree/bindings/input/twl4030-pwrbutton.txt
View File

@ -1,7 +1,7 @@
Texas Instruments TWL family (twl4030) pwrbutton module Texas Instruments TWL family (twl4030) pwrbutton module
This module is part of the TWL4030. For more details about the whole This module is part of the TWL4030. For more details about the whole
chip see Documentation/devicetree/bindings/mfd/twl-familly.txt. chip see Documentation/devicetree/bindings/mfd/twl-family.txt.
This module provides a simple power button event via an Interrupt. This module provides a simple power button event via an Interrupt.

2
Documentation/devicetree/bindings/leds/common.yaml
View File

@ -85,7 +85,7 @@ properties:
# LED will act as a back-light, controlled by the framebuffer system # LED will act as a back-light, controlled by the framebuffer system
- backlight - backlight
# LED will turn on (but for leds-gpio see "default-state" property in # LED will turn on (but for leds-gpio see "default-state" property in
# Documentation/devicetree/bindings/leds/leds-gpio.txt) # Documentation/devicetree/bindings/leds/leds-gpio.yaml)
- default-on - default-on
# LED "double" flashes at a load average based rate # LED "double" flashes at a load average based rate
- heartbeat - heartbeat

2
Documentation/devicetree/bindings/leds/register-bit-led.txt
View File

@ -5,7 +5,7 @@ where single bits in a certain register can turn on/off a
single LED. The register bit LEDs appear as children to the single LED. The register bit LEDs appear as children to the
syscon device, with the proper compatible string. For the syscon device, with the proper compatible string. For the
syscon bindings see: syscon bindings see:
Documentation/devicetree/bindings/mfd/syscon.txt Documentation/devicetree/bindings/mfd/syscon.yaml
Each LED is represented as a sub-node of the syscon device. Each Each LED is represented as a sub-node of the syscon device. Each
node's name represents the name of the corresponding LED. node's name represents the name of the corresponding LED.

2
Documentation/devicetree/bindings/media/ti,cal.yaml
View File

@ -177,7 +177,7 @@ examples:
}; };
}; };
i2c5: i2c@4807c000 { i2c {
clock-frequency = <400000>; clock-frequency = <400000>;
#address-cells = <1>; #address-cells = <1>;
#size-cells = <0>; #size-cells = <0>;

2
Documentation/devicetree/bindings/memory-controllers/ti/emif.txt
View File

@ -32,7 +32,7 @@ Required only for "ti,emif-am3352" and "ti,emif-am4372":
- sram : Phandles for generic sram driver nodes, - sram : Phandles for generic sram driver nodes,
first should be type 'protect-exec' for the driver to use to copy first should be type 'protect-exec' for the driver to use to copy
and run PM functions, second should be regular pool to be used for and run PM functions, second should be regular pool to be used for
data region for code. See Documentation/devicetree/bindings/sram/sram.txt data region for code. See Documentation/devicetree/bindings/sram/sram.yaml
for more details. for more details.
Optional properties: Optional properties:

4
Documentation/devicetree/bindings/mfd/max77650.yaml
View File

@ -97,14 +97,14 @@ examples:
regulators { regulators {
compatible = "maxim,max77650-regulator"; compatible = "maxim,max77650-regulator";
max77650_ldo: regulator@0 { max77650_ldo: regulator-ldo {
regulator-compatible = "ldo"; regulator-compatible = "ldo";
regulator-name = "max77650-ldo"; regulator-name = "max77650-ldo";
regulator-min-microvolt = <1350000>; regulator-min-microvolt = <1350000>;
regulator-max-microvolt = <2937500>; regulator-max-microvolt = <2937500>;
}; };
max77650_sbb0: regulator@1 { max77650_sbb0: regulator-sbb0 {
regulator-compatible = "sbb0"; regulator-compatible = "sbb0";
regulator-name = "max77650-sbb0"; regulator-name = "max77650-sbb0";
regulator-min-microvolt = <800000>; regulator-min-microvolt = <800000>;

4
Documentation/devicetree/bindings/mfd/tps65910.txt
View File

@ -26,8 +26,8 @@ Required properties:
ldo6, ldo7, ldo8 ldo6, ldo7, ldo8
- xxx-supply: Input voltage supply regulator. - xxx-supply: Input voltage supply regulator.
These entries are require if regulators are enabled for a device. Missing of these These entries are required if regulators are enabled for a device. Missing these
properties can cause the regulator registration fails. properties can cause the regulator registration to fail.
If some of input supply is powered through battery or always-on supply then If some of input supply is powered through battery or always-on supply then
also it is require to have these parameters with proper node handle of always also it is require to have these parameters with proper node handle of always
on power supply. on power supply.

0
Documentation/devicetree/bindings/mfd/twl-familly.txt → Documentation/devicetree/bindings/mfd/twl-family.txt
View File

2
Documentation/devicetree/bindings/mfd/zii,rave-sp.txt
View File

@ -20,7 +20,7 @@ RAVE SP consists of the following sub-devices:
Device Description Device Description
------ ----------- ------ -----------
rave-sp-wdt : Watchdog rave-sp-wdt : Watchdog
rave-sp-nvmem : Interface to onborad EEPROM rave-sp-nvmem : Interface to onboard EEPROM
rave-sp-backlight : Display backlight rave-sp-backlight : Display backlight
rave-sp-hwmon : Interface to onboard hardware sensors rave-sp-hwmon : Interface to onboard hardware sensors
rave-sp-leds : Interface to onboard LEDs rave-sp-leds : Interface to onboard LEDs

2
Documentation/devicetree/bindings/misc/fsl,qoriq-mc.txt
View File

@ -26,7 +26,7 @@ For generic IOMMU bindings, see
Documentation/devicetree/bindings/iommu/iommu.txt. Documentation/devicetree/bindings/iommu/iommu.txt.
For arm-smmu binding, see: For arm-smmu binding, see:
Documentation/devicetree/bindings/iommu/arm,smmu.txt. Documentation/devicetree/bindings/iommu/arm,smmu.yaml.
Required properties: Required properties:

1
Documentation/devicetree/bindings/mmc/mmc-controller.yaml
View File

@ -370,6 +370,7 @@ examples:
mmc3: mmc@1c12000 { mmc3: mmc@1c12000 {
#address-cells = <1>; #address-cells = <1>;
#size-cells = <0>; #size-cells = <0>;
reg = <0x1c12000 0x200>;
pinctrl-names = "default"; pinctrl-names = "default";
pinctrl-0 = <&mmc3_pins_a>; pinctrl-0 = <&mmc3_pins_a>;
vmmc-supply = <&reg_vmmc3>; vmmc-supply = <&reg_vmmc3>;

2
Documentation/devicetree/bindings/mtd/cadence-nand-controller.txt
View File

@ -27,7 +27,7 @@ Required properties of NAND chips:
- reg: shall contain the native Chip Select ids from 0 to max supported by - reg: shall contain the native Chip Select ids from 0 to max supported by
the cadence nand flash controller the cadence nand flash controller
See Documentation/devicetree/bindings/mtd/nand.txt for more details on See Documentation/devicetree/bindings/mtd/nand-controller.yaml for more details on
generic bindings. generic bindings.
Example: Example:

2
Documentation/devicetree/bindings/net/brcm,bcm7445-switch-v4.0.txt
View File

@ -45,7 +45,7 @@ Optional properties:
switch queue switch queue
- resets: a single phandle and reset identifier pair. See - resets: a single phandle and reset identifier pair. See
Documentation/devicetree/binding/reset/reset.txt for details. Documentation/devicetree/bindings/reset/reset.txt for details.
- reset-names: If the "reset" property is specified, this property should have - reset-names: If the "reset" property is specified, this property should have
the value "switch" to denote the switch reset line. the value "switch" to denote the switch reset line.

2
Documentation/devicetree/bindings/nvmem/nvmem.yaml
View File

@ -76,6 +76,8 @@ examples:
qfprom: eeprom@700000 { qfprom: eeprom@700000 {
#address-cells = <1>; #address-cells = <1>;
#size-cells = <1>; #size-cells = <1>;
reg = <0x00700000 0x100000>;
wp-gpios = <&gpio1 3 GPIO_ACTIVE_HIGH>; wp-gpios = <&gpio1 3 GPIO_ACTIVE_HIGH>;
/* ... */ /* ... */

2
Documentation/devicetree/bindings/phy/allwinner,sun4i-a10-usb-phy.yaml
View File

@ -86,7 +86,7 @@ examples:
#include <dt-bindings/clock/sun4i-a10-ccu.h> #include <dt-bindings/clock/sun4i-a10-ccu.h>
#include <dt-bindings/reset/sun4i-a10-ccu.h> #include <dt-bindings/reset/sun4i-a10-ccu.h>
usbphy: phy@01c13400 { usbphy: phy@1c13400 {
#phy-cells = <1>; #phy-cells = <1>;
compatible = "allwinner,sun4i-a10-usb-phy"; compatible = "allwinner,sun4i-a10-usb-phy";
reg = <0x01c13400 0x10>, <0x01c14800 0x4>, <0x01c1c800 0x4>; reg = <0x01c13400 0x10>, <0x01c14800 0x4>, <0x01c1c800 0x4>;

2
Documentation/devicetree/bindings/pinctrl/aspeed,ast2400-pinctrl.yaml
View File

@ -17,7 +17,7 @@ description: |+
"aspeed,ast2400-scu", "syscon", "simple-mfd" "aspeed,ast2400-scu", "syscon", "simple-mfd"
Refer to the the bindings described in Refer to the the bindings described in
Documentation/devicetree/bindings/mfd/syscon.txt Documentation/devicetree/bindings/mfd/syscon.yaml
properties: properties:
compatible: compatible:

2
Documentation/devicetree/bindings/pinctrl/aspeed,ast2500-pinctrl.yaml
View File

@ -18,7 +18,7 @@ description: |+
"aspeed,g5-scu", "syscon", "simple-mfd" "aspeed,g5-scu", "syscon", "simple-mfd"
Refer to the the bindings described in Refer to the the bindings described in
Documentation/devicetree/bindings/mfd/syscon.txt Documentation/devicetree/bindings/mfd/syscon.yaml
properties: properties:
compatible: compatible:

2
Documentation/devicetree/bindings/pinctrl/aspeed,ast2600-pinctrl.yaml
View File

@ -17,7 +17,7 @@ description: |+
"aspeed,ast2600-scu", "syscon", "simple-mfd" "aspeed,ast2600-scu", "syscon", "simple-mfd"
Refer to the the bindings described in Refer to the the bindings described in
Documentation/devicetree/bindings/mfd/syscon.txt Documentation/devicetree/bindings/mfd/syscon.yaml
properties: properties:
compatible: compatible:

2
Documentation/devicetree/bindings/pinctrl/st,stm32-pinctrl.yaml
View File

@ -248,7 +248,7 @@ examples:
}; };
//Example 3 pin groups //Example 3 pin groups
pinctrl@60020000 { pinctrl {
usart1_pins_a: usart1-0 { usart1_pins_a: usart1-0 {
pins1 { pins1 {
pinmux = <STM32_PINMUX('A', 9, AF7)>; pinmux = <STM32_PINMUX('A', 9, AF7)>;

2
Documentation/devicetree/bindings/power/amlogic,meson-ee-pwrc.yaml
View File

@ -18,7 +18,7 @@ description: |+
"amlogic,meson-gx-hhi-sysctrl", "simple-mfd", "syscon" "amlogic,meson-gx-hhi-sysctrl", "simple-mfd", "syscon"
Refer to the the bindings described in Refer to the the bindings described in
Documentation/devicetree/bindings/mfd/syscon.txt Documentation/devicetree/bindings/mfd/syscon.yaml
properties: properties:
compatible: compatible:

33
Documentation/devicetree/bindings/power/domain-idle-state.txt
View File

@ -1,33 +0,0 @@
PM Domain Idle State Node:
A domain idle state node represents the state parameters that will be used to
select the state when there are no active components in the domain.
The state node has the following parameters -
- compatible:
Usage: Required
Value type: <string>
Definition: Must be "domain-idle-state".
- entry-latency-us
Usage: Required
Value type: <prop-encoded-array>
Definition: u32 value representing worst case latency in
microseconds required to enter the idle state.
The exit-latency-us duration may be guaranteed
only after entry-latency-us has passed.
- exit-latency-us
Usage: Required
Value type: <prop-encoded-array>
Definition: u32 value representing worst case latency
in microseconds required to exit the idle state.
- min-residency-us
Usage: Required
Value type: <prop-encoded-array>
Definition: u32 value representing minimum residency duration
in microseconds after which the idle state will yield
power benefits after overcoming the overhead in entering
i the idle state.

64
Documentation/devicetree/bindings/power/domain-idle-state.yaml 100644
View File

@ -0,0 +1,64 @@
# SPDX-License-Identifier: GPL-2.0
%YAML 1.2
---
$id: http://devicetree.org/schemas/power/domain-idle-state.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: PM Domain Idle States binding description
maintainers:
- Ulf Hansson <ulf.hansson@linaro.org>
description:
A domain idle state node represents the state parameters that will be used to
select the state when there are no active components in the PM domain.
properties:
$nodename:
const: domain-idle-states
patternProperties:
"^(cpu|cluster|domain)-":
type: object
description:
Each state node represents a domain idle state description.
properties:
compatible:
const: domain-idle-state
entry-latency-us:
description:
The worst case latency in microseconds required to enter the idle
state. Note that, the exit-latency-us duration may be guaranteed only
after the entry-latency-us has passed.
exit-latency-us:
description:
The worst case latency in microseconds required to exit the idle
state.
min-residency-us:
description:
The minimum residency duration in microseconds after which the idle
state will yield power benefits, after overcoming the overhead while
entering the idle state.
required:
- compatible
- entry-latency-us
- exit-latency-us
- min-residency-us
examples:
- |
domain-idle-states {
domain_retention: domain-retention {
compatible = "domain-idle-state";
entry-latency-us = <20>;
exit-latency-us = <40>;
min-residency-us = <80>;
};
};
...

24
Documentation/devicetree/bindings/power/power-domain.yaml
View File

@ -25,22 +25,20 @@ description: |+
properties: properties:
$nodename: $nodename:
pattern: "^(power-controller|power-domain)(@.*)?$" pattern: "^(power-controller|power-domain)([@-].*)?$"
domain-idle-states: domain-idle-states:
$ref: /schemas/types.yaml#/definitions/phandle-array $ref: /schemas/types.yaml#/definitions/phandle-array
description: description: |
A phandle of an idle-state that shall be soaked into a generic domain Phandles of idle states that defines the available states for the
power state. The idle state definitions are compatible with power-domain provider. The idle state definitions are compatible with the
domain-idle-state specified in domain-idle-state bindings, specified in ./domain-idle-state.yaml.
Documentation/devicetree/bindings/power/domain-idle-state.txt
phandles that are not compatible with domain-idle-state will be ignored. Note that, the domain-idle-state property reflects the idle states of this
The domain-idle-state property reflects the idle state of this PM domain PM domain and not the idle states of the devices or sub-domains in the PM
and not the idle states of the devices or sub-domains in the PM domain. domain. Devices and sub-domains have their own idle states independent of
Devices and sub-domains have their own idle-states independent the parent domain's idle states. In the absence of this property, the
of the parent domain's idle states. In the absence of this property, domain would be considered as capable of being powered-on or powered-off.
the domain would be considered as capable of being powered-on
or powered-off.
operating-points-v2: operating-points-v2:
$ref: /schemas/types.yaml#/definitions/phandle-array $ref: /schemas/types.yaml#/definitions/phandle-array

2
Documentation/devicetree/bindings/power/power_domain.txt
View File

@ -109,4 +109,4 @@ Example:
required-opps = <&domain1_opp_1>; required-opps = <&domain1_opp_1>;
}; };
[1]. Documentation/devicetree/bindings/power/domain-idle-state.txt [1]. Documentation/devicetree/bindings/power/domain-idle-state.yaml

2
Documentation/devicetree/bindings/regulator/regulator.yaml
View File

@ -191,7 +191,7 @@ patternProperties:
examples: examples:
- | - |
xyzreg: regulator@0 { xyzreg: regulator {
regulator-min-microvolt = <1000000>; regulator-min-microvolt = <1000000>;
regulator-max-microvolt = <2500000>; regulator-max-microvolt = <2500000>;
regulator-always-on; regulator-always-on;

2
Documentation/devicetree/bindings/reset/st,stm32mp1-rcc.txt
View File

@ -3,4 +3,4 @@ STMicroelectronics STM32MP1 Peripheral Reset Controller
The RCC IP is both a reset and a clock controller. The RCC IP is both a reset and a clock controller.
Please see Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.txt Please see Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml

2
Documentation/devicetree/bindings/sound/st,stm32-sai.txt
View File

@ -36,7 +36,7 @@ SAI subnodes required properties:
- clock-names: Must contain "sai_ck". - clock-names: Must contain "sai_ck".
Must also contain "MCLK", if SAI shares a master clock, Must also contain "MCLK", if SAI shares a master clock,
with a SAI set as MCLK clock provider. with a SAI set as MCLK clock provider.
- dmas: see Documentation/devicetree/bindings/dma/stm32-dma.txt - dmas: see Documentation/devicetree/bindings/dma/st,stm32-dma.yaml
- dma-names: identifier string for each DMA request line - dma-names: identifier string for each DMA request line
"tx": if sai sub-block is configured as playback DAI "tx": if sai sub-block is configured as playback DAI
"rx": if sai sub-block is configured as capture DAI "rx": if sai sub-block is configured as capture DAI

2
Documentation/devicetree/bindings/sound/st,stm32-spdifrx.txt
View File

@ -10,7 +10,7 @@ Required properties:
- clock-names: must contain "kclk" - clock-names: must contain "kclk"
- interrupts: cpu DAI interrupt line - interrupts: cpu DAI interrupt line
- dmas: DMA specifiers for audio data DMA and iec control flow DMA - dmas: DMA specifiers for audio data DMA and iec control flow DMA
See STM32 DMA bindings, Documentation/devicetree/bindings/dma/stm32-dma.txt See STM32 DMA bindings, Documentation/devicetree/bindings/dma/st,stm32-dma.yaml
- dma-names: two dmas have to be defined, "rx" and "rx-ctrl" - dma-names: two dmas have to be defined, "rx" and "rx-ctrl"
Optional properties: Optional properties:

2
Documentation/devicetree/bindings/spi/st,stm32-spi.yaml
View File

@ -49,7 +49,7 @@ properties:
dmas: dmas:
description: | description: |
DMA specifiers for tx and rx dma. DMA fifo mode must be used. See DMA specifiers for tx and rx dma. DMA fifo mode must be used. See
the STM32 DMA bindings Documentation/devicetree/bindings/dma/stm32-dma.txt. the STM32 DMA bindings Documentation/devicetree/bindings/dma/st,stm32-dma.yaml.
items: items:
- description: rx DMA channel - description: rx DMA channel
- description: tx DMA channel - description: tx DMA channel

2
Documentation/devicetree/bindings/sram/allwinner,sun4i-a10-system-control.yaml
View File

@ -125,7 +125,7 @@ examples:
#size-cells = <1>; #size-cells = <1>;
ranges; ranges;
sram_a: sram@00000000 { sram_a: sram@0 {
compatible = "mmio-sram"; compatible = "mmio-sram";
reg = <0x00000000 0xc000>; reg = <0x00000000 0xc000>;
#address-cells = <1>; #address-cells = <1>;

2
Documentation/devicetree/bindings/thermal/brcm,avs-ro-thermal.yaml
View File

@ -17,7 +17,7 @@ description: |+
"brcm,bcm2711-avs-monitor", "syscon", "simple-mfd" "brcm,bcm2711-avs-monitor", "syscon", "simple-mfd"
Refer to the the bindings described in Refer to the the bindings described in
Documentation/devicetree/bindings/mfd/syscon.txt Documentation/devicetree/bindings/mfd/syscon.yaml
properties: properties:
compatible: compatible:

2
Documentation/devicetree/bindings/timer/allwinner,sun4i-a10-timer.yaml
View File

@ -87,7 +87,7 @@ additionalProperties: false
examples: examples:
- | - |
timer { timer@1c20c00 {
compatible = "allwinner,sun4i-a10-timer"; compatible = "allwinner,sun4i-a10-timer";
reg = <0x01c20c00 0x400>; reg = <0x01c20c00 0x400>;
interrupts = <22>, interrupts = <22>,

15
MAINTAINERS
View File

@ -693,7 +693,7 @@ ALLWINNER CPUFREQ DRIVER
M: Yangtao Li <tiny.windzz@gmail.com> M: Yangtao Li <tiny.windzz@gmail.com>
L: linux-pm@vger.kernel.org L: linux-pm@vger.kernel.org
S: Maintained S: Maintained
F: Documentation/devicetree/bindings/opp/sun50i-nvmem-cpufreq.txt F: Documentation/devicetree/bindings/opp/allwinner,sun50i-h6-operating-points.yaml
F: drivers/cpufreq/sun50i-cpufreq-nvmem.c F: drivers/cpufreq/sun50i-cpufreq-nvmem.c
ALLWINNER CRYPTO DRIVERS ALLWINNER CRYPTO DRIVERS
@ -4017,7 +4017,7 @@ M: Cheng-Yi Chiang <cychiang@chromium.org>
S: Maintained S: Maintained
R: Enric Balletbo i Serra <enric.balletbo@collabora.com> R: Enric Balletbo i Serra <enric.balletbo@collabora.com>
R: Guenter Roeck <groeck@chromium.org> R: Guenter Roeck <groeck@chromium.org>
F: Documentation/devicetree/bindings/sound/google,cros-ec-codec.txt F: Documentation/devicetree/bindings/sound/google,cros-ec-codec.yaml
F: sound/soc/codecs/cros_ec_codec.* F: sound/soc/codecs/cros_ec_codec.*
CIRRUS LOGIC AUDIO CODEC DRIVERS CIRRUS LOGIC AUDIO CODEC DRIVERS
@ -4475,7 +4475,7 @@ L: linux-media@vger.kernel.org
T: git git://linuxtv.org/media_tree.git T: git git://linuxtv.org/media_tree.git
S: Maintained S: Maintained
F: drivers/media/platform/sunxi/sun6i-csi/ F: drivers/media/platform/sunxi/sun6i-csi/
F: Documentation/devicetree/bindings/media/sun6i-csi.txt F: Documentation/devicetree/bindings/media/allwinner,sun6i-a31-csi.yaml
CW1200 WLAN driver CW1200 WLAN driver
M: Solomon Peachy <pizza@shaftnet.org> M: Solomon Peachy <pizza@shaftnet.org>
@ -5668,7 +5668,7 @@ L: dri-devel@lists.freedesktop.org
T: git git://anongit.freedesktop.org/drm/drm-misc T: git git://anongit.freedesktop.org/drm/drm-misc
S: Maintained S: Maintained
F: drivers/gpu/drm/stm F: drivers/gpu/drm/stm
F: Documentation/devicetree/bindings/display/st,stm32-ltdc.txt F: Documentation/devicetree/bindings/display/st,stm32-ltdc.yaml
DRM DRIVERS FOR TI LCDC DRM DRIVERS FOR TI LCDC
M: Jyri Sarha <jsarha@ti.com> M: Jyri Sarha <jsarha@ti.com>
@ -10164,7 +10164,7 @@ MAXBOTIX ULTRASONIC RANGER IIO DRIVER
M: Andreas Klinger <ak@it-klinger.de> M: Andreas Klinger <ak@it-klinger.de>
L: linux-iio@vger.kernel.org L: linux-iio@vger.kernel.org
S: Maintained S: Maintained
F: Documentation/devicetree/bindings/iio/proximity/maxbotix,mb1232.txt F: Documentation/devicetree/bindings/iio/proximity/maxbotix,mb1232.yaml
F: drivers/iio/proximity/mb1232.c F: drivers/iio/proximity/mb1232.c
MAXIM MAX77650 PMIC MFD DRIVER MAXIM MAX77650 PMIC MFD DRIVER
@ -10467,7 +10467,7 @@ M: Hugues Fruchet <hugues.fruchet@st.com>
L: linux-media@vger.kernel.org L: linux-media@vger.kernel.org
T: git git://linuxtv.org/media_tree.git T: git git://linuxtv.org/media_tree.git
S: Supported S: Supported
F: Documentation/devicetree/bindings/media/st,stm32-dcmi.txt F: Documentation/devicetree/bindings/media/st,stm32-dcmi.yaml
F: drivers/media/platform/stm32/stm32-dcmi.c F: drivers/media/platform/stm32/stm32-dcmi.c
MEDIA DRIVERS FOR NVIDIA TEGRA - VDE MEDIA DRIVERS FOR NVIDIA TEGRA - VDE
@ -12952,7 +12952,6 @@ M: Robert Richter <rrichter@marvell.com>
L: linux-pci@vger.kernel.org L: linux-pci@vger.kernel.org
L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers) L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
S: Supported S: Supported
F: Documentation/devicetree/bindings/pci/pci-thunder-*
F: drivers/pci/controller/pci-thunder-* F: drivers/pci/controller/pci-thunder-*
PCIE DRIVER FOR HISILICON PCIE DRIVER FOR HISILICON
@ -15922,7 +15921,7 @@ F: drivers/*/stm32-*timer*
F: drivers/pwm/pwm-stm32* F: drivers/pwm/pwm-stm32*
F: include/linux/*/stm32-*tim* F: include/linux/*/stm32-*tim*
F: Documentation/ABI/testing/*timer-stm32 F: Documentation/ABI/testing/*timer-stm32
F: Documentation/devicetree/bindings/*/stm32-*timer* F: Documentation/devicetree/bindings/*/*stm32-*timer*
F: Documentation/devicetree/bindings/pwm/pwm-stm32* F: Documentation/devicetree/bindings/pwm/pwm-stm32*
STMMAC ETHERNET DRIVER STMMAC ETHERNET DRIVER

2
drivers/staging/wfx/Documentation/devicetree/bindings/net/wireless/siliabs,wfx.txt
View File

@ -93,5 +93,5 @@ Some properties are recognized either by SPI and SDIO versions:
Must contains 64 hexadecimal digits. Not supported in current version. Must contains 64 hexadecimal digits. Not supported in current version.
WFx driver also supports `mac-address` and `local-mac-address` as described in WFx driver also supports `mac-address` and `local-mac-address` as described in
Documentation/devicetree/binding/net/ethernet.txt Documentation/devicetree/bindings/net/ethernet.txt