diff options
| author | Ahmad Fatoum <a.fatoum@pengutronix.de> | 2020-06-18 11:10:50 +0200 |
|---|---|---|
| committer | Sascha Hauer <s.hauer@pengutronix.de> | 2020-06-23 09:55:26 +0200 |
| commit | 395e7ce8d3276ca0db45f0727fad655dfb5bc9b2 (patch) | |
| tree | 68a22f9fad029d6bbc2abc57d17e86e00956ad6d /dts/Bindings/media | |
| parent | 2b62fd9f118812da5ebc5c53f25939f2c819e8df (diff) | |
| download | barebox-395e7ce8d3276ca0db45f0727fad655dfb5bc9b2.tar.gz barebox-395e7ce8d3276ca0db45f0727fad655dfb5bc9b2.tar.xz | |
ARM: dts: align all applicable memory nodes with spec and convention
The spec[1] says that top level memory nodes `shall have device_type =
"memory"'. Since 8226f7f9 ("of: base: parse all available memory nodes"),
we parse only nodes with device_type = "memory", so we should add the
device_type property where ever it's missing. When the nodes were first
added, this wasn't an issue because the skeleton.dtsi defined a memory
skeleton with correct device_type, but this was removed upstream and
imported into barebox along with 1dc748b3 ("dts: update to v5.1-rc1").
Upstream device trees with a memory node were adapted to have
device_type = "memory" in-line. This wasn't the case for nodes defined
only within barebox. Rectify this now and rename the nodes to feature a
unit name as well to be aligned with the upstream trend.
[1]: https://github.com/devicetree-org/devicetree-specification/releases/download/v0.3/devicetree-specification-v0.3.pdf
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'dts/Bindings/media')
0 files changed, 0 insertions, 0 deletions