From: Yao Zi <me@ziyao.cc>
To: wjjsn <wjjsn@qq.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
chenhuacai@kernel.org
Cc: kernel@xen0n.name, devicetree@vger.kernel.org,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
wjjsn <2858482031@qq.com>
Subject: Re: [PATCH v5 0/2] Add Loongson-2K0300 processor support
Date: Sun, 22 Mar 2026 12:35:35 +0000 [thread overview]
Message-ID: <ab_iF2hjZRfp16HP@pie> (raw)
In-Reply-To: <tencent_325FB1D2C600CD55E367332EC453E5A64B09@qq.com>
On Sun, Mar 22, 2026 at 03:13:14PM +0800, wjjsn wrote:
> From: wjjsn <2858482031@qq.com>
>
> The first patch adds the necessary DT binding documentation,
> and the second patch adds the DTS and DTSI files for the SoC
> and the board.
Please note I'm working on basic drivers/devicetree for 2K0300
platform[1][2][3], though the series haven't been updated for some
time... I've re-written the pinctrl part, and will try to re-spin all of
them next weekend.
Also, previously Huacai expressed preference on delaying devicetree
changes until basic drivers are ready[4], so anyway we should probably
get driver patches merged first.
Regards,
Yao Zi
[1]: https://lore.kernel.org/all/20250523095408.25919-4-ziyao@disroot.org/
[2]: https://lore.kernel.org/all/20250811163749.47028-2-ziyao@disroot.org/
[3]: https://lore.kernel.org/all/20250816033327.11359-2-ziyao@disroot.org/
[4]: https://lore.kernel.org/all/CAAhV-H6EDEf3U6w5KY3R3HCAdAbqDefqpE3ktCQeQtFbDK2Ypg@mail.gmail.com/
next prev parent reply other threads:[~2026-03-22 12:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 7:13 [PATCH v5 0/2] Add Loongson-2K0300 processor support wjjsn
2026-03-22 12:35 ` Yao Zi [this message]
2026-03-22 13:15 ` Huacai Chen
2026-03-22 16:33 ` wjjsn
2026-03-23 2:42 ` Yao Zi
2026-03-24 15:09 ` wjjsn
2026-03-24 15:23 ` wjjsn
2026-03-24 16:55 ` Yao Zi
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=ab_iF2hjZRfp16HP@pie \
--to=me@ziyao.cc \
--cc=2858482031@qq.com \
--cc=chenhuacai@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@xen0n.name \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=robh@kernel.org \
--cc=wjjsn@qq.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