From: Yixun Lan <dlan@gentoo.org>
To: Bin Meng <bmeng.cn@gmail.com>
Cc: Guo Ren <guoren@kernel.org>,
u-boot@lists.denx.de, Rick Chen <rick@andestech.com>,
Leo <ycliang@andestech.com>, Wei Fu <wefu@redhat.com>,
Jisheng Zhang <jszhang@kernel.org>
Subject: Re: [RESEND PATCH v1 1/4] riscv: t-head: licheepi4a: initial support added
Date: Mon, 29 May 2023 11:10:34 +0800 [thread overview]
Message-ID: <ZHQXqnjMjChMfNoU@ofant> (raw)
In-Reply-To: <CAEUhbmUWqHCQf8b4NnCJCdPKKBg_Cj-GpZkufuG60OTe42V+wQ@mail.gmail.com>
Hi Bin:
On 09:12 Mon 29 May , Bin Meng wrote:
> On Sat, May 27, 2023 at 9:41 PM Yixun Lan <dlan@gentoo.org> wrote:
> >
> > Hi Guo, Jisheng:
> >
> > On 11:36 Sat 27 May , Guo Ren wrote:
> > > On Fri, May 26, 2023 at 8:41 PM Yixun Lan <dlan@gentoo.org> wrote:
> > > >
> > > > Add support for Sipeed's Lichee Pi 4A board which based on
> > > > T-HEAD's TH1520 SoC, only minimal device tree and serial onsole are enabled,
> > > > so it's capable of chain booting from T-HEAD's vendor u-boot.
> > > >
> > > > Reviewed-by: Wei Fu <wefu@redhat.com>
> > > > Signed-off-by: Yixun Lan <dlan@gentoo.org>
> > > > ---
> > > > arch/riscv/Kconfig | 5 ++++
> > > > board/thead/th1520_lpi4a/Kconfig | 42 ++++++++++++++++++++++++++++
> > > > board/thead/th1520_lpi4a/MAINTAINERS | 7 +++++
> > > > board/thead/th1520_lpi4a/Makefile | 5 ++++
> > > > board/thead/th1520_lpi4a/board.c | 14 ++++++++++
> > > > include/configs/th1520_lpi4a.h | 22 +++++++++++++++
> > > > 6 files changed, 95 insertions(+)
> > > > create mode 100644 board/thead/th1520_lpi4a/Kconfig
> > > > create mode 100644 board/thead/th1520_lpi4a/MAINTAINERS
> > > > create mode 100644 board/thead/th1520_lpi4a/Makefile
> > > > create mode 100644 board/thead/th1520_lpi4a/board.c
> > > > create mode 100644 include/configs/th1520_lpi4a.h
> > > >
> > > > diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
> > > > index f6ed05906a..419b6171a9 100644
> > > > --- a/arch/riscv/Kconfig
> > > > +++ b/arch/riscv/Kconfig
> > > > @@ -27,6 +27,10 @@ config TARGET_SIFIVE_UNMATCHED
> > > > config TARGET_STARFIVE_VISIONFIVE2
> > > > bool "Support StarFive VisionFive2 Board"
> > > >
> > > > +config TARGET_TH1520_LPI4A
> > > > + bool "Support Sipeed's TH1520 Lichee PI 4A Board"
> > > > + select SYS_CACHE_SHIFT_6
> > > > +
> > > > config TARGET_SIPEED_MAIX
> > > > bool "Support Sipeed Maix Board"
> > > > select SYS_CACHE_SHIFT_6
> > > > @@ -66,6 +70,7 @@ source "board/emulation/qemu-riscv/Kconfig"
> > > > source "board/microchip/mpfs_icicle/Kconfig"
> > > > source "board/sifive/unleashed/Kconfig"
> > > > source "board/sifive/unmatched/Kconfig"
> > > > +source "board/thead/th1520_lpi4a/Kconfig"
> > > > source "board/openpiton/riscv64/Kconfig"
> > > > source "board/sipeed/maix/Kconfig"
> > > > source "board/starfive/visionfive2/Kconfig"
> > > > diff --git a/board/thead/th1520_lpi4a/Kconfig b/board/thead/th1520_lpi4a/Kconfig
> > > > new file mode 100644
> > > > index 0000000000..622246127c
> > > > --- /dev/null
> > > > +++ b/board/thead/th1520_lpi4a/Kconfig
> > > > @@ -0,0 +1,42 @@
> > > > +if TARGET_TH1520_LPI4A
> > > > +
> > > > +config ARCH_THEAD
> > > > + bool
> > > > + default y
> > > > +
> > > > +config SYS_BOARD
> > > > + default "th1520_lpi4a"
> > for the board, I'm not sure whether people will prefer to keep the 'th1520_' prefix,
> > otherwise we could make it shorter, leave only 'lpi4a'? thoughts?
> >
> > > > +
> > > > +config SYS_VENDOR
> > > > + default "thread"
> > ~~~~~~~ notice, in my original patch, it's 'thead'
> > > default "T-HEAD"
> > No, here should be 'thead', since the CONFIG_SYS_VENDOR will form
> > board/${CONFIG_SYS_VENDOR}, please consult arch/Kconfig for reference.
> >
> > I personally would prefer 't-head' which probably cause less confusion..
> > but since kernel use 'thead'[1], so I just follow it to keep them aligned.
> >
>
> But you have a typo here :)
do you mean 'thread'? It's 'thead' actually in my original patch, so no typo..
I was already trying to clarify this.
It's probably a grammar correction when Guo reply the email
https://lore.kernel.org/all/20230526124107.894-2-dlan@gentoo.org/
>
> > [1] in kernel, the dts path consist of 'thead', e.g. arch/riscv/boot/dts/thead/
> >
>
> Regards,
> Bin
--
Yixun Lan (dlan)
Gentoo Linux Developer
GPG Key ID AABEFD55
next prev parent reply other threads:[~2023-05-29 3:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 12:41 [RESEND PATCH v1 0/4] riscv: Initial support for Lichee PI 4A board Yixun Lan
2023-05-26 12:41 ` [RESEND PATCH v1 1/4] riscv: t-head: licheepi4a: initial support added Yixun Lan
2023-05-27 1:45 ` Guo Ren
2023-05-27 10:51 ` Yixun Lan
2023-05-27 3:36 ` Guo Ren
2023-05-27 11:08 ` Yixun Lan
2023-05-29 1:12 ` Bin Meng
2023-05-29 3:10 ` Yixun Lan [this message]
2023-05-29 4:31 ` Bin Meng
2023-06-29 2:55 ` Leo Liang
2023-07-07 14:05 ` Yixun Lan
2023-05-26 12:41 ` [RESEND PATCH v1 2/4] riscv: dts: t-head: Add basic device tree for Sipeed Lichee PI 4A board Yixun Lan
2023-05-27 1:43 ` Guo Ren
2023-05-27 9:17 ` Yixun Lan
2023-05-29 1:19 ` Guo Ren
2023-05-29 3:00 ` Yixun Lan
2023-05-29 6:50 ` Guo Ren
2023-05-29 7:54 ` Yixun Lan
2023-05-29 8:22 ` Guo Ren
2023-05-29 8:48 ` Yixun Lan
2023-05-26 12:41 ` [RESEND PATCH v1 3/4] configs: th1520_lpi4a_defconfig: Add initial config Yixun Lan
2023-05-26 12:41 ` [RESEND PATCH v1 4/4] doc: t-head: lpi4a: document Lichee PI 4A board Yixun Lan
2023-06-29 2:59 ` Leo Liang
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=ZHQXqnjMjChMfNoU@ofant \
--to=dlan@gentoo.org \
--cc=bmeng.cn@gmail.com \
--cc=guoren@kernel.org \
--cc=jszhang@kernel.org \
--cc=rick@andestech.com \
--cc=u-boot@lists.denx.de \
--cc=wefu@redhat.com \
--cc=ycliang@andestech.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