public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
	Conor Dooley <conor@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>
Cc: linux-riscv@lists.infradead.org
Subject: Re: [PATCH 1/2] riscv: dts: canaan: Clean up serial aliases
Date: Thu, 9 May 2024 15:56:08 +0900	[thread overview]
Message-ID: <04db5556-a404-4fbf-aca8-3b8f066c1f47@kernel.org> (raw)
In-Reply-To: <ac93f18200c5e3f878907084a7c660ee60591db2.1715163174.git.geert+renesas@glider.be>

On 5/8/24 7:20 PM, Geert Uytterhoeven wrote:
> The SoC-specific k210.dtsi declares aliases for all four serial ports.
> However, none of the board-specific DTS files configure pin control for
> any but the first serial port, so the last three ports are not usable.
> 
> Move the aliases node from the SoC-specific k210.dtsi to the
> board-specific DTS files, as these are really board-specific, and retain
> the sole port that is usable.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>

Looks good to me.

Reviewed-by: Damien Le Moal <dlemoal@kernel.org>

-- 
Damien Le Moal
Western Digital Research


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

  reply	other threads:[~2024-05-09  6:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-08 10:20 [PATCH 0/2] riscv: dts: canaan: Unused devices cleanup Geert Uytterhoeven
2024-05-08 10:20 ` [PATCH 1/2] riscv: dts: canaan: Clean up serial aliases Geert Uytterhoeven
2024-05-09  6:56   ` Damien Le Moal [this message]
2024-05-08 10:20 ` [PATCH 2/2] riscv: dts: canaan: Disable I/O devices unless used Geert Uytterhoeven
2024-05-09  6:58   ` Damien Le Moal
2024-05-28 11:26 ` [PATCH 0/2] riscv: dts: canaan: Unused devices cleanup Conor Dooley

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=04db5556-a404-4fbf-aca8-3b8f066c1f47@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    /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