From: Conor Dooley <conor@kernel.org>
To: q691800735@163.com
Cc: linux-riscv@lists.infradead.org, pjw@kernel.org,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr
Subject: Re: [PATCH] riscv: configs: defconfig: Add initial Kendryte K230 defconfig
Date: Wed, 3 Dec 2025 09:54:07 +0000 [thread overview]
Message-ID: <20251203-virtuous-lumpish-587130b6f2ee@spud> (raw)
In-Reply-To: <20251203020619.16496-1-q691800735@163.com>
[-- Attachment #1.1: Type: text/plain, Size: 810 bytes --]
On Wed, Dec 03, 2025 at 10:06:19AM +0800, q691800735@163.com wrote:
> From: jybruceupup <q691800735@163.com>
>
> Add initial defconfig for the Kendryte K230 RISC-V SoC.
> This configuration enables core features for basic boot and functionality:
> - Essential RISC-V architecture support (64-bit, S-mode, page tables)
> - Boot-critical peripherals (UART, GPIO, MMC, clock controller)
> - Device Tree overlay support
> - Basic power management and reset functionality
>
> This defconfig serves as the base for K230-based platforms (including
> CanMV DongshanPi) and maintains compatibility with upstream RISC-V
> kernel features.
>
> Signed-off-by: jybruceupup <q691800735@163.com>
I replied to this yesteday:
https://lore.kernel.org/linux-riscv/20251202-choice-crudely-b7775c3e452d@spud/
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-12-03 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 2:06 [PATCH] riscv: configs: defconfig: Add initial Kendryte K230 defconfig q691800735
2025-12-03 9:54 ` Conor Dooley [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=20251203-virtuous-lumpish-587130b6f2ee@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=q691800735@163.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