From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/4] arm64: dts: Add Qualcomm MSM8916 SoC and evaluation board dts
Date: Fri, 13 Mar 2015 16:25:16 +0000 [thread overview]
Message-ID: <20150313162516.GA9603@leverpostej> (raw)
In-Reply-To: <04AD8E46-277D-4652-88AF-D16538C2AA87@codeaurora.org>
On Fri, Mar 13, 2015 at 03:50:42PM +0000, Kumar Gala wrote:
>
> On Mar 13, 2015, at 5:52 AM, Mark Rutland <mark.rutland@arm.com> wrote:
>
> >> +/ {
> >> + chosen {
> >> + stdout-path = &blsp1_uart2;
> >> + };
> >
> > It would be good if we had the configuration too (see
> > Documentation/devicetree/bindings/chosen.txt), as that avoids any
> > reliance on kernel defaults.
> >
> > You can refer to an alias, so this could be:
> >
> > aliases {
> > serial0 = &blsp1_uart2;
> > };
> >
> > chosen {
> > stdout-path = "serial0:115200n8";
> > };
> >
> > ...assuming that 115200n8 is correct for your UART, of course.
> >
> >
> > [?]
>
> Where is the code that actually handles this parsing? I?m not see it
> in early_init_dt_scan_chosen_serial and I don?t believe
> fdt_path_offset does anything special with ?:'
Take a look at commit 7914a7c5651a5161 ("of: support passing console options with
stdout-path").
Early on of_alias_scan will find the options and in of_console_check
we'll call add_preferred_console as appropriate. That'll be called in
uart_add_one_port.
> I?ll kill off usage of skeleton.dtsi
Cheers.
Mark.
next prev parent reply other threads:[~2015-03-13 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 17:56 [PATCH v4 2/4] arm64: dts: Add Qualcomm MSM8916 SoC and evaluation board dts Kumar Gala
2015-03-13 10:52 ` Mark Rutland
2015-03-13 15:50 ` Kumar Gala
2015-03-13 16:25 ` Mark Rutland [this message]
2015-03-13 16:43 ` Kumar Gala
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=20150313162516.GA9603@leverpostej \
--to=mark.rutland@arm.com \
--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).