From: zajec5@gmail.com (Rafał Miłecki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: dts: BCM5301X: Specify serial console parameters
Date: Tue, 14 Mar 2017 13:32:48 +0100 [thread overview]
Message-ID: <3345fb38-fbea-141e-6ad2-a3341e2c31fe@gmail.com> (raw)
In-Reply-To: <20170314122650.GV15842@lunn.ch>
On 03/14/2017 01:26 PM, Andrew Lunn wrote:
> On Tue, Mar 14, 2017 at 08:58:29AM +0100, Rafa?? Mi??ecki wrote:
>> From: Rafa?? Mi??ecki <rafal@milecki.pl>
>>
>> This adds baud rate, parity & number of data bits. It's required to get
>> serial working correctly.
>>
>> Signed-off-by: Rafa?? Mi??ecki <rafal@milecki.pl>
>> ---
>> arch/arm/boot/dts/bcm5301x.dtsi | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/arm/boot/dts/bcm5301x.dtsi b/arch/arm/boot/dts/bcm5301x.dtsi
>> index 8fd1ef9f0c2d..468107166a6f 100644
>> --- a/arch/arm/boot/dts/bcm5301x.dtsi
>> +++ b/arch/arm/boot/dts/bcm5301x.dtsi
>> @@ -18,8 +18,12 @@
>> / {
>> interrupt-parent = <&gic>;
>>
>> + aliases {
>> + serial0 = &uart0;
>> + };
>> +
>> chosen {
>> - stdout-path = &uart0;
>> + stdout-path = "serial0:115200n8";
>> };
>
> Hi Rafal
>
> The alias is fine. But putting the stdout-path here is unusual. Which
> serial port is used for console is board specific, where as
> bcm5301x.dtsi is very generic, it describes the SoC, not a board. If
> you look at other .dtsi files, those that specify stdout-path contain
> properties which are common to a range of similar boards.
So far I've never seen any board using other uart. Also uart0 is disabled by
default and we enable it per board family (BCM4708 / BCM47081 / BCM4709 /
BCM47094). I think it's just more practical to have simple DTS that covers
99,9% boards by default and handled that margin of devices separately.
We already got a lot of duplicated code for enabling uart0, see:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7b790d3b2943bf8e7e7bafe184008bd6451fe0bd
Jon Mason from Broadcom who knows this hardware and designs very well confirmed
it's a sane/safe assumption.
next prev parent reply other threads:[~2017-03-14 12:32 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 [this message]
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 ` [PATCH V2 1/2] ARM: dts: BCM5301X: Specify serial console params in dtsi files Florian Fainelli
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=3345fb38-fbea-141e-6ad2-a3341e2c31fe@gmail.com \
--to=zajec5@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).