From: Christoffer Dall <christoffer.dall-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>,
Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Benjamin Herrenschmidt
<benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>,
Rob Herring <rob.herring-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: [RFC 0/5] of: Automatic console registration cleanups
Date: Fri, 28 Mar 2014 13:58:36 -0700 [thread overview]
Message-ID: <20140328205836.GN25519@cbox> (raw)
In-Reply-To: <CAL_JsqKFO+OSz83f=XdyKgCqByUvHe7qLzgn5QLU1x1V1A5Fng-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, Mar 28, 2014 at 02:19:23PM -0500, Rob Herring wrote:
> On Fri, Mar 28, 2014 at 1:56 PM, Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org> 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.
> >>
> >> The one downside with this approach is that it doesn't do anything for
> >> early console setup. That still needs to be added on a per-driver basis,
> >> but at least it shouldn't conflict with this approach.
>
> I'm working on the early aspect. I've got things working with either
> command line (which I sent out recently) and with parsing the FDT
> (which I haven't sent out yet).
>
> > Looks sane to me (as discussed in person). I gave it a run on PWRficient with
> > and without console= line (8250-based uart), and it behaved as expected.
> >
> > A couple of nits on the series, replied to two of the patches.
> >
> > I'll give it a run through the board farm here too, but I'll keep console=
> > bootargs there for those boots at this time, too much to change to take it out
> > everywhere. :-)
>
> It would be good to know if removing console= causes userspace any
> issues. For example, if getty's were setup based on console params. I
> know ubuntu does some detection of serial ports, but I don't recall
> what it looks at. Hopefully it's just checking /dev nodes.
>
In Ubuntu, recent versions at least, it's all just hardcoded in
/etc/init/*.conf files. The Linaro OE FS does check /proc/cmdline for
console= in there - not sure if we care, or at least we can have it
fixed quickly.
-Christoffer
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Christoffer Dall <christoffer.dall@linaro.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Olof Johansson <olof@lixom.net>,
Grant Likely <grant.likely@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Rob Herring <rob.herring@linaro.org>
Subject: Re: [RFC 0/5] of: Automatic console registration cleanups
Date: Fri, 28 Mar 2014 13:58:36 -0700 [thread overview]
Message-ID: <20140328205836.GN25519@cbox> (raw)
In-Reply-To: <CAL_JsqKFO+OSz83f=XdyKgCqByUvHe7qLzgn5QLU1x1V1A5Fng@mail.gmail.com>
On Fri, Mar 28, 2014 at 02:19:23PM -0500, Rob Herring wrote:
> On Fri, Mar 28, 2014 at 1:56 PM, Olof Johansson <olof@lixom.net> 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.
> >>
> >> The one downside with this approach is that it doesn't do anything for
> >> early console setup. That still needs to be added on a per-driver basis,
> >> but at least it shouldn't conflict with this approach.
>
> I'm working on the early aspect. I've got things working with either
> command line (which I sent out recently) and with parsing the FDT
> (which I haven't sent out yet).
>
> > Looks sane to me (as discussed in person). I gave it a run on PWRficient with
> > and without console= line (8250-based uart), and it behaved as expected.
> >
> > A couple of nits on the series, replied to two of the patches.
> >
> > I'll give it a run through the board farm here too, but I'll keep console=
> > bootargs there for those boots at this time, too much to change to take it out
> > everywhere. :-)
>
> It would be good to know if removing console= causes userspace any
> issues. For example, if getty's were setup based on console params. I
> know ubuntu does some detection of serial ports, but I don't recall
> what it looks at. Hopefully it's just checking /dev nodes.
>
In Ubuntu, recent versions at least, it's all just hardcoded in
/etc/init/*.conf files. The Linaro OE FS does check /proc/cmdline for
console= in there - not sure if we care, or at least we can have it
fixed quickly.
-Christoffer
next prev parent reply other threads:[~2014-03-28 20:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 16:08 [RFC 0/5] of: Automatic console registration cleanups Grant Likely
2014-03-28 16:08 ` 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: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-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 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 16:08 ` Grant Likely
2014-03-28 18:56 ` [RFC 0/5] of: Automatic console registration cleanups Olof Johansson
2014-03-28 18:56 ` Olof Johansson
[not found] ` <20140328185653.GB26433-O5ziIzlqnXUVNXGz7ipsyg@public.gmane.org>
2014-03-28 19:19 ` Rob Herring
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 [this message]
2014-03-28 20:58 ` Christoffer Dall
2014-03-28 23:50 ` Grant Likely
2014-03-28 23:50 ` Grant Likely
2014-03-28 23:53 ` Grant Likely
2014-03-28 23:53 ` Grant Likely
2014-06-12 1:28 ` Rob Herring
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
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-29 0:32 ` 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
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=20140328205836.GN25519@cbox \
--to=christoffer.dall-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org \
--cc=rob.herring-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.