From: Leo Liang <ycliang@andestech.com>
To: Thomas Bonnefille <thomas.bonnefille@bootlin.com>
Cc: "Peng Fan" <peng.fan@nxp.com>,
"Jaehoon Chung" <jh80.chung@samsung.com>,
"Tom Rini" <trini@konsulko.com>, "Rick Chen" <rick@andestech.com>,
"Kongyang Liu" <seashell11234455@gmail.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Miquèl Raynal" <miquel.raynal@bootlin.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH 2/3] riscv: dts: sophgo: add device tree for LicheeRV Nano
Date: Mon, 25 Nov 2024 17:59:57 +0800 [thread overview]
Message-ID: <Z0RKnfpS5d4I5QbG@swlinux02> (raw)
In-Reply-To: <D5QFYNC0TNVT.11K9SURYSS7W1@bootlin.com>
On Tue, Nov 19, 2024 at 09:35:32PM +0100, Thomas Bonnefille wrote:
> [EXTERNAL MAIL]
>
> On Mon Nov 18, 2024 at 11:01 AM CET, Leo Liang wrote:
> > On Tue, Nov 12, 2024 at 03:57:37PM +0100, Thomas Bonnefille wrote:
> > > [EXTERNAL MAIL]
> > >
> > > Import a slightly modified version of the LicheeRV Nano and SG2002
> > > device trees from the Linux Kernel. The current supported IPs are UART,
> > > MMC, Timer, PLIC and CLINT.
> > >
> > > Signed-off-by: Thomas Bonnefille <thomas.bonnefille@bootlin.com>
> > > ---
> > > arch/riscv/dts/Makefile | 1 +
> > > arch/riscv/dts/sg2002-licheerv-nano-b.dts | 45 +++++++++++++++++++++++++++++++
> > > arch/riscv/dts/sg2002.dtsi | 34 +++++++++++++++++++++++
> > > 3 files changed, 80 insertions(+)
> >
> > Hi Thomas,
> >
> > Could we switch to use OF_UPSTREAM ?
> >
>
> Hello Leo,
>
> Thank you for your review, I have a question though.
>
> The LicheeRV Nano device tree isn't upstreamed yet. It's just in the
> Sophgo SoC maintainer tree and should be merged in v6.13 so in ~10 weeks.
> Can I keep it out of dts/upstream for the moment or should I merge it by
> hand before ?
Hi Thomas,
Got it! So there should be a follow-up patch that
switch to OF_UPSTREAM once the upstream LicheeRV Nano DTS is settled, right?
I can take this patch as is for now. Thanks!
Best regards,
Leo
next prev parent reply other threads:[~2024-11-25 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 14:57 [PATCH 0/3] Add support for LicheeRV Nano Thomas Bonnefille
2024-11-12 14:57 ` [PATCH 1/3] doc: add LicheeRV Nano and SG2002 SoC Thomas Bonnefille
2024-11-18 9:49 ` Leo Liang
2024-11-12 14:57 ` [PATCH 2/3] riscv: dts: sophgo: add device tree for LicheeRV Nano Thomas Bonnefille
2024-11-18 10:01 ` Leo Liang
2024-11-19 20:35 ` Thomas Bonnefille
2024-11-25 9:59 ` Leo Liang [this message]
2024-11-27 9:05 ` Thomas Bonnefille
2024-11-12 14:57 ` [PATCH 3/3] board: add support " Thomas Bonnefille
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=Z0RKnfpS5d4I5QbG@swlinux02 \
--to=ycliang@andestech.com \
--cc=jh80.chung@samsung.com \
--cc=miquel.raynal@bootlin.com \
--cc=peng.fan@nxp.com \
--cc=rick@andestech.com \
--cc=seashell11234455@gmail.com \
--cc=thomas.bonnefille@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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