From: Leo Liang <ycliang@andestech.com>
To: Yao Zi <ziyao@disroot.org>
Cc: Tom Rini <trini@konsulko.com>, Rick Chen <rick@andestech.com>,
Wei Fu <wefu@redhat.com>, Yixun Lan <dlan@gentoo.org>,
<u-boot@lists.denx.de>, "Han Gao" <rabenda.cn@gmail.com>,
Han Gao <gaohan@iscas.ac.cn>
Subject: Re: [PATCH 1/3] pinctrl: Port pin controller driver for T-Head TH1520 SoC
Date: Thu, 3 Jul 2025 18:01:15 +0800 [thread overview]
Message-ID: <aGZU6-HW7sYG71An@swlinux02> (raw)
In-Reply-To: <20250618095457.45926-2-ziyao@disroot.org>
On Wed, Jun 18, 2025 at 09:54:55AM +0000, Yao Zi wrote:
> The SoC pads of TH1520 are separated into three groups (AP 1, AP 2 and
> AON) controlled by independent pin controllers. This patch ports their
> driver from Linux kernel with most code for setting pinconf and pinmux
> kept as is.
>
> The dt-binding of TH1520 pin controller uses a schema where pins to
> configure are specfied as strings and looked up at runtime, which the
> generic pinctrl helpers of U-Boot cannot parse, thus a customized
> set_state() callback is implemented to parse pinconfig nodes and setup
> the configuration.
>
> Signed-off-by: Yao Zi <ziyao@disroot.org>
> ---
> MAINTAINERS | 1 +
> drivers/pinctrl/Kconfig | 8 +
> drivers/pinctrl/Makefile | 1 +
> drivers/pinctrl/pinctrl-th1520.c | 700 +++++++++++++++++++++++++++++++
> 4 files changed, 710 insertions(+)
> create mode 100644 drivers/pinctrl/pinctrl-th1520.c
Acked-by: Leo Yu-Chi Liang <ycliang@andestech.com>
next prev parent reply other threads:[~2025-07-03 10:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 9:54 [PATCH 0/3] Add pinctrl support for TH1520 SoC Yao Zi
2025-06-18 9:54 ` [PATCH 1/3] pinctrl: Port pin controller driver for T-Head " Yao Zi
2025-07-03 10:01 ` Leo Liang [this message]
2025-06-18 9:54 ` [PATCH 2/3] riscv: dts: th1520: Add pin controllers Yao Zi
2025-07-03 10:02 ` Leo Liang
2025-06-18 9:54 ` [PATCH 3/3] riscv: cpu: th1520: Enable pinctrl by default Yao Zi
2025-07-03 10:03 ` 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=aGZU6-HW7sYG71An@swlinux02 \
--to=ycliang@andestech.com \
--cc=dlan@gentoo.org \
--cc=gaohan@iscas.ac.cn \
--cc=rabenda.cn@gmail.com \
--cc=rick@andestech.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=wefu@redhat.com \
--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.