linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Yao Zi <ziyao@disroot.org>
To: Drew Fustini <fustini@kernel.org>, Guo Ren <guoren@kernel.org>,
	Fu Wei <wefu@redhat.com>, Philipp Zabel <p.zabel@pengutronix.de>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>,
	Michal Wilczynski <m.wilczynski@samsung.com>
Cc: devicetree@vger.kernel.org, Han Gao <gaohan@iscas.ac.cn>,
	linux-kernel@vger.kernel.org, Han Gao <rabenda.cn@gmail.com>,
	linux-riscv@lists.infradead.org, Yao Zi <ziyao@disroot.org>
Subject: [PATCH v2 0/3] Scope TH1520 reset driver to VO subsystem
Date: Wed, 20 Aug 2025 07:42:42 +0000	[thread overview]
Message-ID: <20250820074245.16613-1-ziyao@disroot.org> (raw)

T-Head TH1520 SoC integrates nine distinct reset controllers (AON, AP,
DDR, MISC, VI, VO, VP, DSP and AUDIO). Currently only the reset
controller for the VO (Video Output) subsystem is implemented in
mainline Linux.

However, the controller is described with a generic compatible string
"thead,th1520-reset", which may imply control over all reset signals
on the SoC and thus is confusing. It may also cause conflicts when
reset support for other subsystems are introduced.

This series deprecates the generic "thead,th1520-reset" compatible
string, documents a new one, "thead,th1520-reset-vo", which explicitly
describes scope of the reset controller, and converts driver and
devicetree to use the new one.

Krzysztof and Drew, I agree that we should document the bindings for
other reset controllers in TH1520 ASAP, but this requires a lot of new
code: taking TEE-only ones into account, there're eight new controllers
to be documented. Since this is a fix series that may be backported, it
think it may help to keep it small, thus decided to make a separate
series for the new reset controllers.

Changed from v1
- Split the original patch
- Deprecate the old compatible instead of removing it in dt-binding
- Drop the redundant label and outer SoC node for the dt-binding
  example
  - Keep the old compatible in driver for compatibility
  - Link to v1: https://lore.kernel.org/all/20250810-fix_reset_2-v1-1-b0d1900ba578@samsung.com/

Yao Zi (3):
  dt-bindings: reset: Scope the compatible to VO subsystem explicitly
  reset: th1520: Support the new compatible for VO-subsystem controller
  riscv: dts: thead: Scope the reset controller to VO for TH1520

 .../bindings/reset/thead,th1520-reset.yaml      | 17 ++++++++---------
 arch/riscv/boot/dts/thead/th1520.dtsi           |  6 +++---
 drivers/reset/reset-th1520.c                    |  1 +
 3 files changed, 12 insertions(+), 12 deletions(-)

-- 
2.50.1


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

             reply	other threads:[~2025-08-20  7:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-20  7:42 Yao Zi [this message]
2025-08-20  7:42 ` [PATCH v2 1/3] dt-bindings: reset: Scope the compatible to VO subsystem explicitly Yao Zi
2025-08-21  7:54   ` Krzysztof Kozlowski
2025-08-22  8:28     ` Yao Zi
2025-08-22  9:45       ` Krzysztof Kozlowski
2025-08-20  7:42 ` [PATCH v2 2/3] reset: th1520: Support the new compatible for VO-subsystem controller Yao Zi
2025-08-21  7:50   ` Krzysztof Kozlowski
2025-08-20  7:42 ` [PATCH v2 3/3] riscv: dts: thead: Scope the reset controller to VO for TH1520 Yao Zi
2025-08-21  7:49   ` Krzysztof Kozlowski

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=20250820074245.16613-1-ziyao@disroot.org \
    --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).