devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Liviu Dudau <liviu.dudau@arm.com>
Cc: Rob Herring <robh@kernel.org>,
	devicetree@vger.kernel.org,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH] arm: dts: vexpress: Set chosen 'stdout-path'
Date: Fri, 1 Oct 2021 10:25:05 +0100	[thread overview]
Message-ID: <20211001092505.sboaxhc5eobo4u3o@bogus> (raw)
In-Reply-To: <YVSG784Ev71DUZyR@e110455-lin.cambridge.arm.com>

On Wed, Sep 29, 2021 at 04:31:59PM +0100, Liviu Dudau wrote:
> Hi Rob,
> 
> On Fri, Sep 24, 2021 at 04:48:44PM -0500, Rob Herring wrote:
> > Using chosen 'stdout-path' is the preferred way to set the console, but
> > several Arm, Ltd. platforms don't set it. Set it to the 1st serial port.
> > 
> > Cc: Liviu Dudau <liviu.dudau@arm.com>
> > Cc: Sudeep Holla <sudeep.holla@arm.com>
> > Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> > Cc: linux-arm-kernel@lists.infradead.org
> > Signed-off-by: Rob Herring <robh@kernel.org>
> > ---
> > RFC because I don't have any idea what the baud rate is for real boards. 
> > If anyone knows, please comment and I'll add it.
> 
> I believe all of them default to 115200,8n1 but I'm only sure about the first two
> boards.
> 

Sorry to contradict, but I ran TC2 this Monday with 38400 baud. So the first
four must be 38400, as the uart is in the MB IOFPGA and we just change the
coretile DB to get the first 4 platforms. Juno and N1SDP have SoC uart and
they are configured by default to 115200 IIUC.

-- 
Regards,
Sudeep

  reply	other threads:[~2021-10-01  9:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24 21:48 [RFC PATCH] arm: dts: vexpress: Set chosen 'stdout-path' Rob Herring
2021-09-29 15:31 ` Liviu Dudau
2021-10-01  9:25   ` Sudeep Holla [this message]
2021-10-01 16:31     ` Liviu Dudau

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=20211001092505.sboaxhc5eobo4u3o@bogus \
    --to=sudeep.holla@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=liviu.dudau@arm.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=robh@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).