From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] OF: Add helper for matching against linux, stdout-path
Date: Thu, 22 Nov 2012 15:31:52 +0000 [thread overview]
Message-ID: <20121122153152.2B9CB3E129E@localhost> (raw)
In-Reply-To: <20121122054138.GY4398@game.jcrosoft.org>
On Thu, 22 Nov 2012 06:41:38 +0100, Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com> wrote:
> On 18:03 Wed 21 Nov , Grant Likely wrote:
> > On Wed, Nov 21, 2012 at 3:57 PM, Jean-Christophe PLAGNIOL-VILLARD
> > <plagnioj@jcrosoft.com> wrote:
> > > From: Sascha Hauer <s.hauer@pengutronix.de>
> > >
> > > devicetrees may have a linux,stdout-path or stdout-path property
> > > in the chosen node describing the console device. This adds a helper
> > > function to match a device against this property and retrieve the options
> > > so a driver can call add_preferred_console for a matching device.
> >
> > NIce. Looks like the right behaviour, but is a little inefficient.
> > Since the stdout property doesn't change this code could be called
> > once right after the tree is unflattened and then cache the pointer to
> > the node anarguments. Can you add the code to of_alias_scan()?
> do we assume that we can have only one stdout-path?
>
> I think we could have more serial, framebuffer console
Nope. stdout-path as currently defined is only one device. Someone would
need to propose an extension for multiple stdout's before I'd bother
trying to support that.
g.
next prev parent reply other threads:[~2012-11-22 15:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 15:53 [PATCH v5] linux,stdout-path helper Jean-Christophe PLAGNIOL-VILLARD
2012-11-21 15:57 ` [PATCH 1/4] OF: Add helper for matching against linux,stdout-path Jean-Christophe PLAGNIOL-VILLARD
2012-11-21 15:57 ` [PATCH 2/4] serial: i.MX: Make console support non optional Jean-Christophe PLAGNIOL-VILLARD
2012-11-21 15:57 ` [PATCH 3/4] serial: i.MX: evaluate linux,stdout-path property Jean-Christophe PLAGNIOL-VILLARD
2012-11-21 15:57 ` [PATCH 4/4] tty: Atmel serial: add linux,stdout-path support Jean-Christophe PLAGNIOL-VILLARD
2012-11-21 17:26 ` [PATCH 1/4] OF: Add helper for matching against linux, stdout-path Sascha Hauer
2012-11-22 5:33 ` Lothar Waßmann
2012-11-21 18:03 ` Grant Likely
2012-11-22 5:41 ` [PATCH 1/4] OF: Add helper for matching against linux,stdout-path Jean-Christophe PLAGNIOL-VILLARD
2012-11-22 15:31 ` Grant Likely [this message]
2012-11-22 19:35 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-22 21:21 ` [PATCH 1/4] OF: Add helper for matching against linux, stdout-path Grant Likely
2013-07-23 14:17 ` [PATCH v5] linux,stdout-path helper Sascha Hauer
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=20121122153152.2B9CB3E129E@localhost \
--to=grant.likely@secretlab.ca \
--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 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).