From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/15] ARM: dts: kirkwood: add stdout-path property to all boards
Date: Thu, 1 May 2014 09:30:01 +0200 [thread overview]
Message-ID: <20140501073001.GI3082@lunn.ch> (raw)
In-Reply-To: <142642785.6KSg8q4tJP@wuerfel>
On Wed, Apr 30, 2014 at 10:30:21PM +0200, Arnd Bergmann wrote:
> 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.
OK, then i can add my
Acked-by: Andrew Lunn <andrew@lunn.ch>
I will try to do some testing over the weekend.
Andrew
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Lunn <andrew@lunn.ch>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Andrew Lunn <andrew@lunn.ch>, Mark Rutland <mark.rutland@arm.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Russell King <linux@arm.linux.org.uk>,
Jason Cooper <jason@lakedaemon.net>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
Kumar Gala <galak@codeaurora.org>,
Gregory Clement <gregory.clement@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 03/15] ARM: dts: kirkwood: add stdout-path property to all boards
Date: Thu, 1 May 2014 09:30:01 +0200 [thread overview]
Message-ID: <20140501073001.GI3082@lunn.ch> (raw)
In-Reply-To: <142642785.6KSg8q4tJP@wuerfel>
On Wed, Apr 30, 2014 at 10:30:21PM +0200, Arnd Bergmann wrote:
> 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.
OK, then i can add my
Acked-by: Andrew Lunn <andrew@lunn.ch>
I will try to do some testing over the weekend.
Andrew
next prev parent reply other threads:[~2014-05-01 7:30 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 12:56 [PATCH 00/15] Kirkwood DT fix and cleanup round 1 Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` [PATCH 01/15] ARM: dts: kirkwood: fix mislocated pcie-controller nodes Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-05-05 0:46 ` Jason Cooper
2014-05-05 0:46 ` Jason Cooper
2014-05-05 0:46 ` Jason Cooper
2014-05-05 22:20 ` Adam Baker
2014-05-05 22:20 ` Adam Baker
2014-04-30 12:56 ` [PATCH 02/15] ARM: dts: kirkwood: add node labels Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-05-05 0:56 ` Jason Cooper
2014-05-05 0:56 ` Jason Cooper
2014-05-05 0:56 ` Jason Cooper
2014-04-30 12:56 ` [PATCH 03/15] ARM: dts: kirkwood: add stdout-path property to all boards Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 16:38 ` Andrew Lunn
2014-04-30 16:38 ` Andrew Lunn
2014-04-30 16:38 ` Andrew Lunn
2014-04-30 19:47 ` Sebastian Hesselbarth
2014-04-30 19:47 ` Sebastian Hesselbarth
2014-04-30 19:47 ` Sebastian Hesselbarth
2014-04-30 20:21 ` Andrew Lunn
2014-04-30 20:21 ` Andrew Lunn
2014-04-30 20:21 ` Andrew Lunn
2014-04-30 20:30 ` Arnd Bergmann
2014-04-30 20:30 ` Arnd Bergmann
2014-04-30 20:30 ` Arnd Bergmann
2014-05-01 7:30 ` Andrew Lunn [this message]
2014-05-01 7:30 ` Andrew Lunn
2014-04-30 12:56 ` [PATCH 04/15] ARM: dts: kirkwood: remove clock-frequency properties from UART nodes Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` [PATCH 05/15] ARM: dts: kirkwood: rename pin-controller nodes Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` [PATCH 06/15] ARM: dts: kirkwood: add pinctrl node to common SoC include Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` [PATCH 07/15] ARM: dts: kirkwood: consolidate common pinctrl settings Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 16:42 ` Jason Gunthorpe
2014-04-30 16:42 ` Jason Gunthorpe
2014-04-30 16:44 ` Andrew Lunn
2014-04-30 16:44 ` Andrew Lunn
2014-04-30 16:44 ` Andrew Lunn
2014-04-30 19:39 ` Sebastian Hesselbarth
2014-04-30 19:39 ` Sebastian Hesselbarth
2014-04-30 19:39 ` Sebastian Hesselbarth
2014-04-30 19:44 ` Jason Gunthorpe
2014-04-30 19:44 ` Jason Gunthorpe
2014-04-30 19:44 ` Jason Gunthorpe
2014-04-30 19:54 ` Sebastian Hesselbarth
2014-04-30 19:54 ` Sebastian Hesselbarth
2014-04-30 19:54 ` Sebastian Hesselbarth
2014-04-30 12:56 ` [PATCH 08/15] ARM: dts: kirkwood: set default pinctrl for GBE1 Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` [PATCH 09/15] ARM: dts: kirkwood: set default pinctrl for UART0/1 Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` [PATCH 10/15] ARM: dts: kirkwood: set default pinctrl for SPI0 Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` [PATCH 11/15] ARM: dts: kirkwood: set default pinctrl for NAND Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` [PATCH 12/15] ARM: dts: kirkwood: set default pinctrl for I2C0 Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` [PATCH 13/15] ARM: dts: kirkwood: set default pinctrl for I2C1 on 6282 Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` [PATCH 14/15] ARM: dts: kirkwood: set Guruplug ethernet PHY compatible Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 12:56 ` [PATCH 15/15] ARM: dts: kirkwood: set Guruplug phy-connection-type to rgmii-id Sebastian Hesselbarth
2014-04-30 12:56 ` Sebastian Hesselbarth
2014-04-30 16:49 ` [PATCH 00/15] Kirkwood DT fix and cleanup round 1 Andrew Lunn
2014-04-30 16:49 ` Andrew Lunn
2014-04-30 16:49 ` Andrew Lunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140501073001.GI3082@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.