From: Yao Zi <ziyao@disroot.org>
To: Drew Fustini <fustini@kernel.org>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Albert Ou <aou@eecs.berkeley.edu>,
Michal Wilczynski <m.wilczynski@samsung.com>,
Alexandre Ghiti <alex@ghiti.fr>,
devicetree@vger.kernel.org, Han Gao <gaohan@iscas.ac.cn>,
Han Gao <rabenda.cn@gmail.com>,
linux-kernel@vger.kernel.org, Guo Ren <guoren@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-riscv@lists.infradead.org, Fu Wei <wefu@redhat.com>
Subject: Re: [PATCH v3 3/5] reset: th1520: Prepare for supporting multiple controllers
Date: Wed, 29 Oct 2025 15:13:46 +0000 [thread overview]
Message-ID: <aQIvH4jbj9Ifd7Av@pie> (raw)
In-Reply-To: <aQIOgbUf2IHoWCf2@gen8>
On Wed, Oct 29, 2025 at 12:54:25PM +0000, Drew Fustini wrote:
> On Tue, Oct 14, 2025 at 01:10:30PM +0000, Yao Zi wrote:
> > TH1520 SoC is divided into several subsystems, shipping distinct reset
> > controllers with similar control logic. Let's make reset signal mapping
> > a data structure specific to one compatible to prepare for introduction
> > of more reset controllers in the future.
> >
> > Signed-off-by: Yao Zi <ziyao@disroot.org>
> > ---
> > drivers/reset/reset-th1520.c | 42 +++++++++++++++++++++++++-----------
> > 1 file changed, 30 insertions(+), 12 deletions(-)
> >
> > diff --git a/drivers/reset/reset-th1520.c b/drivers/reset/reset-th1520.c
> > index 14d964a9c6b6..2b65a95ed021 100644
> > --- a/drivers/reset/reset-th1520.c
> > +++ b/drivers/reset/reset-th1520.c
> [snip]
> > @@ -138,22 +147,31 @@ static int th1520_reset_probe(struct platform_device *pdev)
> > if (IS_ERR(priv->map))
> > return PTR_ERR(priv->map);
> >
> > - /* Initialize GPU resets to asserted state */
> > - ret = regmap_update_bits(priv->map, TH1520_GPU_RST_CFG,
> > - TH1520_GPU_RST_CFG_MASK, 0);
> > - if (ret)
> > - return ret;
> > + if (of_device_is_compatible(dev->of_node, "thead,th1520-reset")) {
>
> Is there a reason that there is a now a conditional check for the
> compatible here?
Yes, this regmap operation is for initializing GPU resets and thus
modifies TH1520_GPU_RST_CFG, which only applies for the VO reset
controller (with compatible "thead,th1520-reset") but not others, or
other unrelated resets could be unexpectedly asserted.
> Thanks,
> Drew
Regards,
Yao Zi
next prev parent reply other threads:[~2025-10-29 15:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 13:10 [PATCH v3 0/5] Add reset controllers for other TH1520 subsystems Yao Zi
2025-10-14 13:10 ` [PATCH v3 1/5] dt-bindings: reset: thead,th1520-reset: Remove non-VO-subsystem resets Yao Zi
2025-10-15 1:09 ` Guo Ren
2025-10-29 12:34 ` Drew Fustini
2025-10-14 13:10 ` [PATCH v3 2/5] dt-bindings: reset: thead,th1520-reset: Add controllers for more subsys Yao Zi
2025-10-15 1:05 ` Guo Ren
2025-10-29 12:38 ` Drew Fustini
2025-10-14 13:10 ` [PATCH v3 3/5] reset: th1520: Prepare for supporting multiple controllers Yao Zi
2025-10-15 1:03 ` Guo Ren
2025-10-29 12:54 ` Drew Fustini
2025-10-29 15:13 ` Yao Zi [this message]
2025-10-30 12:17 ` Drew Fustini
2025-10-14 13:10 ` [PATCH v3 4/5] reset: th1520: Support reset controllers in more subsystems Yao Zi
2025-10-15 1:06 ` Guo Ren
2025-10-29 12:52 ` Drew Fustini
2025-10-14 13:10 ` [PATCH v3 5/5] riscv: dts: thead: Add reset controllers of more subsystems for TH1520 Yao Zi
2025-10-15 1:07 ` Guo Ren
2025-10-27 11:56 ` Drew Fustini
2025-10-28 13:42 ` Yao Zi
2025-10-29 12:50 ` Drew Fustini
2025-11-01 9:59 ` Drew Fustini
2025-10-30 12:55 ` [PATCH v3 0/5] Add reset controllers for other TH1520 subsystems Philipp Zabel
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=aQIvH4jbj9Ifd7Av@pie \
--to=ziyao@disroot.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fustini@kernel.org \
--cc=gaohan@iscas.ac.cn \
--cc=guoren@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=m.wilczynski@samsung.com \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rabenda.cn@gmail.com \
--cc=robh@kernel.org \
--cc=wefu@redhat.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).