devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@linaro.org>
To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	robh@kernel.org, olof@lixom.net, benh@kernel.crashing.org
Subject: [PATCH 0/4] of Automatic console registration cleanups
Date: Wed, 18 Jun 2014 21:54:30 +0100	[thread overview]
Message-ID: <1403124874-19929-1-git-send-email-grant.likely@linaro.org> (raw)

I posted this series a 1.5 months ago as an RFC. I'm going to put it in
my tree for merging in v3.17.

This series cleans 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 that
property points to a serial port node, then when the serial driver
registers he port, the core uart_add_one_port() function will notice
and if no console= argument was provided then add it as a preferred
console.

             reply	other threads:[~2014-06-18 20:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 20:54 Grant Likely [this message]
2014-06-18 20:54 ` [PATCH 1/4] of: Create of_console_check() for selecting a console specified in /chosen Grant Likely
2014-06-18 20:54 ` [PATCH 2/4] of: Enable console on serial ports specified by /chosen/stdout-path Grant Likely
2014-06-18 20:54 ` [PATCH 3/4] arm/versatile: Add the uart as the stdout device Grant Likely
2014-06-18 20:54 ` [PATCH 4/4] tty: Update hypervisor tty drivers to use core stdout parsing code 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=1403124874-19929-1-git-send-email-grant.likely@linaro.org \
    --to=grant.likely@linaro.org \
    --cc=benh@kernel.crashing.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=robh@kernel.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).