From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: dlan@gentoo.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, cyy@cyyself.name,
daniel.lezcano@linaro.org, tglx@linutronix.de,
samuel.holland@sifive.com, anup@brainfault.org,
Greg KH <gregkh@linuxfoundation.org>,
jirislaby@kernel.org, lkundrak@v3.sk, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-serial@vger.kernel.org, jesse@rivosinc.com,
jszhang@kernel.org, inochiama@outlook.com, uwu@icenowy.me,
zhangmeng.kevin@spacemit.com, kevin.z.m@hotmail.com,
Conor Dooley <conor.dooley@microchip.com>,
matthias.bgg@kernel.org
Subject: Re: [PATCH v5 00/10] riscv: add initial support for SpacemiT K1
Date: Tue, 17 Sep 2024 22:08:03 +0100 [thread overview]
Message-ID: <20240917-spoilage-nimble-a8303fd04482@squawk> (raw)
In-Reply-To: <mhng-5bc45db9-5deb-4db6-8733-561768b2968c@palmer-ri-x1c9>
[-- Attachment #1: Type: text/plain, Size: 2755 bytes --]
On Tue, Sep 17, 2024 at 06:04:29AM -0700, Palmer Dabbelt wrote:
> On Mon, 29 Jul 2024 17:28:03 PDT (-0700), dlan@gentoo.org wrote:
> > SpacemiT K1 is an ideal chip for some new extension such as RISC-V Vector
> > 1.0 and Zicond evaluation now. Add initial support for it to allow more
> > people to participate in building drivers to mainline for it.
> >
> > This kernel has been tested upon Banana Pi BPI-F3 board on vendor U-Boot
> > bootflow generated by Armbian SDK[1] and patched OpenSBI[2] to enable
> > Zicboz, which does not in the vendor dts on its U-Boot. Then successfully
> > booted to busybox on initrd with this log[3].
> >
> > As previous discussion in patch v1[4], maintainer expect more basic drivers
> > ready before really merging it, which would be fine. For other follow-up patches,
> > that are clk, pinctrl/gpio, reset.. My current goal would target at a headless
> > system including SD card, emmc, and ethernet.
>
> Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
>
> if you guys want to take this through some SOC tree. I'm not really sure
> what the bar is for SOC support to get merged, but I'd be happy to just see
> this booting at all -- we've got a bunch of them floating around and the
> vendor kernels are pretty crusty, so anything's an improvement on my end.
I've asked for clock and ideally pinctrl support before merging it. We
had a conversation about the usefulness etc of some of the initial
devicetrees merged for some platforms a few months back, that lead to me
not merging the k230 support I had queued up. I know this isn't exactly
a "fair" barrier to entry, as it is likely that platforms supported by
hobbyists are going to be more affected than companies that usually come
with that basic level, but have to draw a line somewhere.
Both clock and pinctrl are currently in progress for the k1, hopefully
wont take too much longer before this is mergeable.
In other news, nobody has really made an "official" statement about who
is going to maintain this particular platform. People have expressed
interest (including the submitter of the series, IIRC) but there's no
MAINTAINERS entry added here AFAICT. I used to have an entry that
covered arch/riscv/boot/dts/*, with exclusions for sunxi and renesas,
but with Drew taking on thead and sophgo being the resぽonsibility of
Chen Wang and Inochi, I no longer have that wildcard.
I'm happy to apply patches for the platform if noone else is interested
in that side of things, provided there are willing reviewers, but I
would much rather that someone else took up the responsibility of
applying patches and sending PRs - and of course I am happy to help
whoever that is with the process.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-09-17 21:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 0:28 [PATCH v5 00/10] riscv: add initial support for SpacemiT K1 Yixun Lan
2024-07-30 0:28 ` [PATCH v5 01/10] dt-bindings: vendor-prefixes: add spacemit Yixun Lan
2024-07-30 0:28 ` [PATCH v5 02/10] dt-bindings: riscv: Add SpacemiT X60 compatibles Yixun Lan
2024-07-30 0:28 ` [PATCH v5 03/10] dt-bindings: riscv: add SpacemiT K1 bindings Yixun Lan
2024-07-30 0:28 ` [PATCH v5 04/10] dt-bindings: timer: Add SpacemiT K1 CLINT Yixun Lan
2024-07-30 0:28 ` [PATCH v5 05/10] dt-bindings: interrupt-controller: Add SpacemiT K1 PLIC Yixun Lan
2024-07-30 0:28 ` [PATCH v5 06/10] dt-bindings: serial: 8250: Add SpacemiT K1 uart compatible Yixun Lan
2024-07-30 0:28 ` [PATCH v5 07/10] riscv: add SpacemiT SoC family Kconfig support Yixun Lan
2024-07-30 0:28 ` [PATCH v5 08/10] riscv: dts: add initial SpacemiT K1 SoC device tree Yixun Lan
2024-08-01 15:57 ` Jesse Taube
2024-07-30 0:28 ` [PATCH v5 09/10] riscv: dts: spacemit: add Banana Pi BPI-F3 board " Yixun Lan
2024-08-01 15:57 ` Jesse Taube
2024-07-30 0:28 ` [PATCH v5 10/10] riscv: defconfig: enable SpacemiT SoC Yixun Lan
2024-09-17 13:04 ` [PATCH v5 00/10] riscv: add initial support for SpacemiT K1 Palmer Dabbelt
2024-09-17 21:08 ` Conor Dooley [this message]
2024-10-18 17:24 ` Conor Dooley
2024-10-18 23:46 ` Yixun Lan
2024-12-11 22:33 ` patchwork-bot+linux-riscv
2024-12-12 10:19 ` Yixun Lan
2024-12-15 15:04 ` Conor Dooley
2024-12-19 1:19 ` Yixun Lan
2025-01-04 2:22 ` (subset) " Yixun Lan
2025-02-03 19:15 ` patchwork-bot+linux-riscv
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=20240917-spoilage-nimble-a8303fd04482@squawk \
--to=conor@kernel.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=cyy@cyyself.name \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@gentoo.org \
--cc=gregkh@linuxfoundation.org \
--cc=inochiama@outlook.com \
--cc=jesse@rivosinc.com \
--cc=jirislaby@kernel.org \
--cc=jszhang@kernel.org \
--cc=kevin.z.m@hotmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=matthias.bgg@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=tglx@linutronix.de \
--cc=uwu@icenowy.me \
--cc=zhangmeng.kevin@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;
as well as URLs for NNTP newsgroup(s).