From: Sascha Hauer <s.hauer@pengutronix.de>
To: Grant Likely <grant.likely@linaro.org>
Cc: devicetree@vger.kernel.org, christoffer.dall@linaro.org,
linux-kernel@vger.kernel.org, olof@lixom.net,
benh@kernel.crashing.org, rob.herring@linaro.org
Subject: Re: [RFC 0/5] of: Automatic console registration cleanups
Date: Tue, 1 Apr 2014 08:12:16 +0200 [thread overview]
Message-ID: <20140401061216.GQ17250@pengutronix.de> (raw)
In-Reply-To: <20140331094124.6DEF3C408E1@trevor.secretlab.ca>
On Mon, Mar 31, 2014 at 10:41:24AM +0100, Grant Likely wrote:
> On Mon, 31 Mar 2014 09:10:15 +0200, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > On Fri, Mar 28, 2014 at 09:08:00AM -0700, Grant Likely wrote:
> > > Hi all,
> > >
> > > This is a series that I've been playing with over the last few days to
> > > clean up the selection of default console devices when using the device
> > > tree. The device tree defines a way of specifying the console by using a
> > > "stdout-path" property in the /chosen node, but very few drivers
> > > actually attempt to use that data, and so for most platforms there needs
> > > to be a "console=" line in the command line if a serial port is intended
> > > to be used as the console.
> > >
> > > With this series, if there is a /chosen/stdout-path property, and if
> > > that property points to a serial port node, then when the serial driver
> > > registers the port, the core uart_add_one_port() function will notice
> > > and if no console= argument was provided then add it as a preferred
> > > console.
> > >
> > > I've not tested this very extensively yet, but I want to get some
> > > feedback before I go further.
> >
> > I gave it a test on i.MX. It works as expected with both
> > linux,stdout-path and stdout-path. Specifying a console on the
> > commandline still works and overrides the devicetree setting.
> >
> > Tested-by: Sascha Hauer <s.hauer@pengutronix.de>
>
> Brilliant! Thanks Sascha.
>
> Can you supply a patch to add stdout to the imx dts files?
The information which console is used on each board is not in the
kernel. I can create a patch adding stdout for a handful of boards I
know, but I won't catch all.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2014-04-01 6:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 16:08 [RFC 0/5] of: Automatic console registration cleanups Grant Likely
[not found] ` < 20140328185653.GB26433@quad.lixom.net>
[not found] ` < CAL_JsqKFO+OSz83f=XdyKgCqByUvHe7qLzgn5QLU1x1V1A5Fng@mail.gmail.com>
[not found] ` < 20140331071014.GN17250@pengutronix.de>
2014-03-28 16:08 ` [RFC 1/5] of: Add support for ePAPR "stdout-path" property Grant Likely
[not found] ` <1396022885-6102-2-git-send-email-grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-03-28 21:33 ` Benjamin Herrenschmidt
2014-03-28 21:56 ` Rob Herring
2014-03-29 21:16 ` Benjamin Herrenschmidt
2014-03-29 0:30 ` Grant Likely
2014-03-28 16:08 ` [RFC 2/5] of: Create of_console_check() for selecting a console specified in /chosen Grant Likely
[not found] ` <1396022885-6102-3-git-send-email-grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-03-28 18:38 ` Olof Johansson
2014-03-28 16:08 ` [RFC 3/5] of: Enable console on serial ports specified by /chosen/stdout-path Grant Likely
[not found] ` <1396022885-6102-1-git-send-email-grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-03-28 16:08 ` [RFC 4/5] arm/versatile: Add the uart as the stdout device Grant Likely
2014-03-28 18:56 ` [RFC 0/5] of: Automatic console registration cleanups Olof Johansson
[not found] ` <20140328185653.GB26433-O5ziIzlqnXUVNXGz7ipsyg@public.gmane.org>
2014-03-28 19:19 ` Rob Herring
[not found] ` <CAL_JsqKFO+OSz83f=XdyKgCqByUvHe7qLzgn5QLU1x1V1A5Fng-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-28 20:58 ` Christoffer Dall
2014-03-28 23:50 ` Grant Likely
2014-03-28 23:53 ` Grant Likely
2014-06-12 1:28 ` Rob Herring
2014-06-12 10:12 ` Grant Likely
2014-03-28 16:08 ` [RFC 5/5] tty: Update hypervisor tty drivers to use core stdout parsing code Grant Likely
2014-03-28 18:54 ` Olof Johansson
[not found] ` < 1396022885-6102-6-git-send-email-grant.likely@linaro.org>
[not found] ` <20140328185443. GA26433@quad.lixom.net>
[not found] ` <20140328185443.GA26433-O5ziIzlqnXUVNXGz7ipsyg@public.gmane.org>
2014-03-28 21:41 ` Grant Likely
[not found] ` < 1396022885-6102-2-git-send-email-grant.likely@linaro.org>
[not found] ` <1396042396.11529 .27.camel@pasglop>
[not found] ` <CAL_Jsq+xTeocLtS9GFWLCkoV+USACma+w0=O_ysekvTGhYVhZg@ mail.gmail.com>
[not found] ` <CAL_Jsq+xTeocLtS9GFWLCkoV+USACma+w0=O_ysekvTGhYVhZg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-29 0:32 ` [RFC 1/5] of: Add support for ePAPR "stdout-path" property Grant Likely
2014-03-31 7:10 ` [RFC 0/5] of: Automatic console registration cleanups Sascha Hauer
2014-03-31 9:41 ` Grant Likely
2014-04-01 6:12 ` Sascha Hauer [this message]
2014-04-01 9:08 ` Grant Likely
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=20140401061216.GQ17250@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=benh@kernel.crashing.org \
--cc=christoffer.dall@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rob.herring@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).