[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140331094124.6DEF3C408E1@trevor.secretlab.ca>
Date: Mon, 31 Mar 2014 10:41:24 +0100
From: Grant Likely <grant.likely@...aro.org>
To: Sascha Hauer <s.hauer@...gutronix.de>
Cc: devicetree@...r.kernel.org, christoffer.dall@...aro.org,
linux-kernel@...r.kernel.org, olof@...om.net,
benh@...nel.crashing.org, rob.herring@...aro.org
Subject: Re: [RFC 0/5] of: Automatic console registration cleanups
On Mon, 31 Mar 2014 09:10:15 +0200, Sascha Hauer <s.hauer@...gutronix.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@...gutronix.de>
Brilliant! Thanks Sascha.
Can you supply a patch to add stdout to the imx dts files?
g.
--
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