devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org,
	Florian Fainelli <f.fainelli@gmail.com>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	Russell King <linux@armlinux.org.uk>,
	Rob Herring <robh+dt@kernel.org>,
	bcm-kernel-feedback-list@broadcom.com,
	Rafa?? Mi??ecki <rafal@milecki.pl>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] ARM: dts: BCM5301X: Specify serial console parameters
Date: Tue, 14 Mar 2017 13:37:13 +0100	[thread overview]
Message-ID: <aab82e4c-803e-34d7-5455-ba905b91bde4@gmail.com> (raw)
In-Reply-To: <3345fb38-fbea-141e-6ad2-a3341e2c31fe@gmail.com>

On 03/14/2017 01:32 PM, Rafał Miłecki wrote:
> 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.

That was supposed to be "any other uart or parameters".

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2017-03-14 12:37 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
     [not found] ` <20170314075830.2247-1-zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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
     [not found]     ` <20170314122650.GV15842-g2DYL2Zd6BY@public.gmane.org>
2017-03-14 12:32       ` Rafał Miłecki
2017-03-14 12:37         ` Rafał Miłecki [this message]
     [not found]         ` <3345fb38-fbea-141e-6ad2-a3341e2c31fe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-14 12:51           ` Andrew Lunn
2017-03-14 14:53         ` Jon Mason
     [not found]           ` <CAC3K-4qQzX37BLD2N-N-vDwSk=H_rF5PzoMM+GM=Z935QFVnXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-14 20:44             ` Scott Branden
     [not found]               ` <9f5a0381-aae6-9ac2-56f3-9eb78ecfd819-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2017-03-14 21:18                 ` Jon Mason
     [not found]                   ` <CAC3K-4pAzs5fXNB=ZpyzYZnTENa=c0v81GVn7WpW53K7GV9UOg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-14 21:28                     ` Scott Branden
     [not found]                       ` <5776ba44-e280-9711-1b05-1c79556884e2-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
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
     [not found]     ` <20170315170328.13879-1-zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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=aab82e4c-803e-34d7-5455-ba905b91bde4@gmail.com \
    --to=zajec5@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=rafal@milecki.pl \
    --cc=robh+dt@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).