Am Dienstag, den 11.08.2015, 11:29 -0600 schrieb Stephen Warren:

On 08/11/2015 11:05 AM, Lucas Stach wrote:

quoted

Hi Simon,

why did you send this to the Tegra ML?

At my request, so that the DT changes could be reviewed by the kernel DT 
reviewers and added to the copy of the DT files in the kernel source 
tree if approved.

This doesn't really answer the question why it was sent to the Tegra
list if it is an RPi change, but that's just a side note.

My assertion is that DT content should be independent of SW stack. Or 
put another way, all SW stacks should use the same DT content. As such, 
if these properties are needed by U-Boot, and contained in the copy of 
the DT files in the U-Boot source tree, they should also be present in 
the copy of the DT files in the kernel source tree, so the two do not 
become out of sync.

I agree with that overall goal to have a common DT base between
different software stacks. After all I lobbied for keeping the Tegra
pinctrl setting in the DT even though Linux doesn't use them any more.

For my question below I honestly want an answer as to why U-Boot needs
those DT changes and why it can't work with the current DT contents.
It's really just the same question we also have to answer for each and
every DT addition that we do for Linux.

Regards,
Lucas

quoted

Am Dienstag, den 11.08.2015, 08:25 -0600 schrieb Simon Glass:

quoted

This updates the device tree from the kernel version to something suitable
for U-Boot:

- Add stdout-path alias for console
- Mark the /soc node to be available pre-relocation so that the early
serial console works (we need the 'ranges' property to be available)

quoted

quoted

diff --git a/arch/arm/boot/dts/bcm2835.dtsi b/arch/arm/boot/dts/bcm2835.dtsi
index 301c73f..bd6bff6 100644
--- a/arch/arm/boot/dts/bcm2835.dtsi
+++ b/arch/arm/boot/dts/bcm2835.dtsi

@@ -8,6 +8,7 @@

  	chosen {
  		bootargs = "earlyprintk console=ttyAMA0";
+		stdout-path = &uart;
  	};

  	soc {

@@ -16,6 +17,7 @@
  		#size-cells = <1>;
  		ranges = <0x7e000000 0x20000000 0x02000000>;
  		dma-ranges = <0x40000000 0x00000000 0x20000000>;
+		u-boot,dm-pre-reloc;

Why do you need this and why should upstream carry your favourite
bootloaders configuration? This is in no way hardware description.