From: Jeremy Kerr <jk@codeconstruct.com.au>
To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Lee Jones <lee@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: Mark Brown <broonie@kernel.org>
Subject: [PATCH v4 0/2] Add reset control for mfd syscon devices
Date: Thu, 5 Jan 2023 08:50:08 +0800 [thread overview]
Message-ID: <20230105005010.124948-1-jk@codeconstruct.com.au> (raw)
This RFC series adds a facility for syscon devices to control a reset
line when probed; we have instances of simple register-only syscon
resources that need deassertion of a reset line for the register set to
be accessible.
Rather than requiring a specific driver to implement this, it'd be nice
to use the generic syscon device and the generic resets linkage to do
so.
Any comments/queries/etc are most welcome.
Cheers,
Jeremy
---
v2:
- use direct syscon registration interface, rather than the (unused)
syscon platform device code
- consequently, add regmap infrastructure to attach a reset
controller, in a similar way to attaching clocks
v3:
- drop regmap reset control and just do a direct deassert from the syscon
driver
v4:
- collapse unnecessary else block in syscon driver reset control
---
Jeremy Kerr (2):
dt-bindings: mfd/syscon: Add resets property
mfd: syscon: allow reset control for syscon devices
.../devicetree/bindings/mfd/syscon.yaml | 3 +++
drivers/mfd/syscon.c | 27 ++++++++++++++-----
2 files changed, 24 insertions(+), 6 deletions(-)
--
2.38.1
next reply other threads:[~2023-01-05 0:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 0:50 Jeremy Kerr [this message]
2023-01-05 0:50 ` [PATCH v4 1/2] dt-bindings: mfd/syscon: Add resets property Jeremy Kerr
2023-01-19 16:29 ` Lee Jones
2023-01-05 0:50 ` [PATCH v4 2/2] mfd: syscon: allow reset control for syscon devices Jeremy Kerr
2023-01-19 16:30 ` Lee Jones
2023-09-12 21:13 ` Daniel Golle
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=20230105005010.124948-1-jk@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.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.