[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <142642785.6KSg8q4tJP@wuerfel>
Date: Wed, 30 Apr 2014 22:30:21 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Andrew Lunn <andrew@...n.ch>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Mark Rutland <mark.rutland@....com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Russell King <linux@....linux.org.uk>,
Jason Cooper <jason@...edaemon.net>,
Pawel Moll <pawel.moll@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>,
Kumar Gala <galak@...eaurora.org>,
Gregory Clement <gregory.clement@...e-electrons.com>,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 03/15] ARM: dts: kirkwood: add stdout-path property to all boards
On Wednesday 30 April 2014 22:21:30 Andrew Lunn wrote:
> > Yes, we *can* move it in kirkwood.dtsi, but IMHO we *should* keep it in
> > the board files. I see the "chosen" node and its properties as _the_
> > board node.
> >
> > One could argue then, that we should count the memory properties too and
> > put the most common in the SoC dtsi. But you are right, as UART0 is also
> > the UART with boot support, it is likely to be always connected to
> > a more-or-less accessible console output.
> >
> > I really have no strong opinion about it.
>
> Me neithe, but the advantage of putting it in kirkwood.dtsi is that it
> then does not get forgotten, and is always there for bearbox to use.
I would prefer having it in the board.dts file out of principle, but I
agree it's not very important either way.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists