From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 1/2] ARM: dts: BCM5301X: Specify serial console params in dtsi files
Date: Wed, 22 Mar 2017 09:49:24 -0700 [thread overview]
Message-ID: <c900cc9c-3650-f6f0-3650-01f05f680fcd@gmail.com> (raw)
In-Reply-To: <20170315170328.13879-1-zajec5@gmail.com>
On 03/15/2017 10:03 AM, Rafa? Mi?ecki wrote:
> From: Rafa? Mi?ecki <rafal@milecki.pl>
>
> So far every Northstar device we have seen was using the same serial
> console params (115200n8). It probably make the most sense to put it in
> some proper dtsi files instead of repeating over and over for every
> single device. As different boards may use different bootloaders it
> seems the safest idea is to use board specific dtsi files.
>
> Just in case some vendor decides to use different UART (parameters) this
> can be always easily overwritten.
>
> Signed-off-by: Rafa? Mi?ecki <rafal@milecki.pl>
Applied, thanks!
--
Florian
prev parent reply other threads:[~2017-03-22 16:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 7:58 [PATCH 1/2] ARM: dts: BCM5301X: Specify serial console parameters Rafał Miłecki
2017-03-14 7:58 ` [PATCH 2/2] ARM: dts: BCM53573: " Rafał Miłecki
2017-03-14 12:26 ` [PATCH 1/2] ARM: dts: BCM5301X: " Andrew Lunn
2017-03-14 12:32 ` Rafał Miłecki
2017-03-14 12:37 ` Rafał Miłecki
2017-03-14 12:51 ` Andrew Lunn
2017-03-14 14:53 ` Jon Mason
2017-03-14 20:44 ` Scott Branden
2017-03-14 21:18 ` Jon Mason
2017-03-14 21:28 ` Scott Branden
2017-03-14 21:51 ` Andrew Lunn
2017-03-15 17:03 ` [PATCH V2 1/2] ARM: dts: BCM5301X: Specify serial console params in dtsi files Rafał Miłecki
2017-03-15 17:03 ` [PATCH V2 2/2] ARM: dts: BCM53573: Specify serial console parameters Rafał Miłecki
2017-03-22 16:49 ` Florian Fainelli [this message]
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=c900cc9c-3650-f6f0-3650-01f05f680fcd@gmail.com \
--to=f.fainelli@gmail.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).