From: Yixun Lan <dlan@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: spacemit@lists.linux.dev,
Conor Dooley <conor.dooley@microchip.com>,
Vivian Wang <wangruikang@iscas.ac.cn>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] dts: spacemit: set console baud rate on bpif3
Date: Tue, 5 May 2026 07:23:48 +0000 [thread overview]
Message-ID: <20260505072348-GKB3537744@kernel.org> (raw)
In-Reply-To: <20260430-reword-overstep-3be08b7eab25@spud>
Hi Conor,
On 19:52 Thu 30 Apr , Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Because the default console's baud rate is not set, defconfig kernels do
> not have any serial output on this platform. Set the baud rate to
> 115200, matching what is used by U-Boot etc on this platform.
>
> Suggested-by: Vivian Wang <wangruikang@iscas.ac.cn>
> Fixes: d60d57ab6b2a8 ("riscv: dts: spacemit: add Banana Pi BPI-F3 board device tree")
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
Reviewed-by: Yixun Lan <dlan@kernel.org>
--
Yixun Lan (dlan)
WARNING: multiple messages have this Message-ID (diff)
From: Yixun Lan <dlan@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: spacemit@lists.linux.dev,
Conor Dooley <conor.dooley@microchip.com>,
Vivian Wang <wangruikang@iscas.ac.cn>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] dts: spacemit: set console baud rate on bpif3
Date: Tue, 5 May 2026 07:23:48 +0000 [thread overview]
Message-ID: <20260505072348-GKB3537744@kernel.org> (raw)
In-Reply-To: <20260430-reword-overstep-3be08b7eab25@spud>
Hi Conor,
On 19:52 Thu 30 Apr , Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Because the default console's baud rate is not set, defconfig kernels do
> not have any serial output on this platform. Set the baud rate to
> 115200, matching what is used by U-Boot etc on this platform.
>
> Suggested-by: Vivian Wang <wangruikang@iscas.ac.cn>
> Fixes: d60d57ab6b2a8 ("riscv: dts: spacemit: add Banana Pi BPI-F3 board device tree")
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
Reviewed-by: Yixun Lan <dlan@kernel.org>
--
Yixun Lan (dlan)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-05-05 7:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 18:52 [PATCH v1] dts: spacemit: set console baud rate on bpif3 Conor Dooley
2026-04-30 18:52 ` Conor Dooley
2026-05-02 12:01 ` Yixun Lan
2026-05-02 12:01 ` Yixun Lan
2026-05-03 17:58 ` Conor Dooley
2026-05-03 17:58 ` Conor Dooley
2026-05-05 7:23 ` Yixun Lan [this message]
2026-05-05 7:23 ` Yixun Lan
2026-05-05 8:53 ` Yixun Lan
2026-05-05 8:53 ` Yixun Lan
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=20260505072348-GKB3537744@kernel.org \
--to=dlan@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=wangruikang@iscas.ac.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.