From: Yixun Lan <dlan@gentoo.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Meng Zhang <zhangmeng.kevin@linux.spacemit.com>,
Inochi Amaoto <inochiama@gmail.com>,
Jesse Taube <mr.bossman075@gmail.com>,
Yangyu Chen <cyy@cyyself.name>,
soc@kernel.org, Conor Dooley <conor@kernel.org>,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [GIT PULL] RISC-V SpacemiT Devicetrees for v6.14
Date: Thu, 16 Jan 2025 23:47:53 +0000 [thread overview]
Message-ID: <20250116234753-GYA20457@gentoo> (raw)
In-Reply-To: <6a8bb914-858e-479d-a7d9-09e0ff688160@app.fastmail.com>
Hi Arnd:
> On Wed, Jan 8, 2025, at 15:21, Yixun Lan wrote:
> > Hi Arnd,
> >
> > Here is SpacemiT's device tree changes for 6.14 cycle.
> > All patches have been merged in linux-next tree for testing.
> >
> >
> > ----------------------------------------------------------------
> > RISC-V SpacemiT DT changes for 6.14
> > - basic device tree support
> > - pinctrl dt node info
> > - update MAINTAINERS info
> >
>
> Sorry for the delay in pulling this. I just had a look and found
> that your branch is based on -rc3 while the soc tree is currently
> using 6.13-rc2. I try hard to avoid unnecessary backmerges of
> upstream contents into my tree, so it would be nice if you could
> rebase it onto 6.13-rc1 or 6.13-rc2 and resend.
>
sorry, I will keep this in mind, and will rebase to 6.13-rc2
> While looking through the contents, I also found a mistake
> in the contents:
>
> +++ b/arch/riscv/boot/dts/spacemit/k1.dtsi
> @@ -0,0 +1,459 @@
> ...
> + aliases {
> + serial0 = &uart0;
> + serial1 = &uart2;
> + serial2 = &uart3;
> + serial3 = &uart4;
> + serial4 = &uart5;
> + serial5 = &uart6;
> + serial6 = &uart7;
> + serial7 = &uart8;
> + serial8 = &uart9;
> + };
>
> The aliases here should be in the k1-bananapi-f3.dts file,
> not in the k1.dtsi file, since the mapping between exposed
> UART devices and those available in the chip is board
> specific. You normally want to list only those devices
> that are marked status="okay" on that board.
>
> I would suggest you fix this in a patch on top of your
> existing commits, but make it part of the pull request.
>
Ok
> Arnd
--
Yixun Lan (dlan)
Gentoo Linux Developer
GPG Key ID AABEFD55
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-01-16 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 14:21 [GIT PULL] RISC-V SpacemiT Devicetrees for v6.14 Yixun Lan
2025-01-16 16:49 ` Arnd Bergmann
2025-01-16 23:47 ` Yixun Lan [this message]
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=20250116234753-GYA20457@gentoo \
--to=dlan@gentoo.org \
--cc=arnd@arndb.de \
--cc=conor@kernel.org \
--cc=cyy@cyyself.name \
--cc=inochiama@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=mr.bossman075@gmail.com \
--cc=soc@kernel.org \
--cc=zhangmeng.kevin@linux.spacemit.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