From: Leo Liang <ycliang@andestech.com>
To: Yao Zi <ziyao@disroot.org>
Cc: Rick Chen <rick@andestech.com>, Tom Rini <trini@konsulko.com>,
"Lukasz Majewski" <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>,
Maksim Kiselev <bigunclemax@gmail.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
Kongyang Liu <seashell11234455@gmail.com>,
Casey Connolly <casey.connolly@linaro.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Simon Glass <sjg@chromium.org>,
Christian Marangi <ansuelsmth@gmail.com>, <u-boot@lists.denx.de>,
Han Gao <rabenda.cn@gmail.com>, Han Gao <gaohan@iscas.ac.cn>
Subject: Re: [PATCH 1/4] riscv: cpu: th1520: Initialize IOPMPs in SPL
Date: Wed, 21 May 2025 16:42:24 +0800 [thread overview]
Message-ID: <aC2R8KYDoF_dOTO7@swlinux02> (raw)
In-Reply-To: <20250516030525.31361-2-ziyao@disroot.org>
On Fri, May 16, 2025 at 03:05:22AM +0000, Yao Zi wrote:
> TH1520 SoC ships several IOPMPs protecting various on-chip peripherals.
> They must be configured before accessing the peripherals. Let's
> initialize them in SPL harts_early_init().
>
> Signed-off-by: Yao Zi <ziyao@disroot.org>
> ---
> arch/riscv/cpu/th1520/spl.c | 65 ++++++++++++++++++++++
> arch/riscv/include/asm/arch-th1520/iopmp.h | 42 ++++++++++++++
> 2 files changed, 107 insertions(+)
> create mode 100644 arch/riscv/include/asm/arch-th1520/iopmp.h
Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>
next prev parent reply other threads:[~2025-05-21 8:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 3:05 [PATCH 0/4] Improve usability of TH1520 with mainline SPL Yao Zi
2025-05-16 3:05 ` [PATCH 1/4] riscv: cpu: th1520: Initialize IOPMPs in SPL Yao Zi
2025-05-21 8:42 ` Leo Liang [this message]
2025-05-16 3:05 ` [PATCH 2/4] clk: thead: Port clock controller driver of TH1520 SoC Yao Zi
2025-05-21 8:43 ` Leo Liang
2025-05-16 3:05 ` [PATCH 3/4] riscv: cpu: th1520: Select clock driver Yao Zi
2025-05-21 8:44 ` Leo Liang
2025-05-16 3:05 ` [PATCH 4/4] riscv: dts: th1520: Complete clock tree Yao Zi
2025-05-21 8:44 ` 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=aC2R8KYDoF_dOTO7@swlinux02 \
--to=ycliang@andestech.com \
--cc=ansuelsmth@gmail.com \
--cc=bigunclemax@gmail.com \
--cc=casey.connolly@linaro.org \
--cc=gaohan@iscas.ac.cn \
--cc=ilias.apalodimas@linaro.org \
--cc=jh80.chung@samsung.com \
--cc=lukma@denx.de \
--cc=neil.armstrong@linaro.org \
--cc=rabenda.cn@gmail.com \
--cc=rick@andestech.com \
--cc=seanga2@gmail.com \
--cc=seashell11234455@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=ziyao@disroot.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.