From: Rob Herring <robh@kernel.org>
To: Jeremy Kerr <jk@codeconstruct.com.au>
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Lee Jones <lee@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [RFC PATCH 1/2] dt-bindings: mfd/syscon: Add resets property
Date: Tue, 6 Dec 2022 07:09:43 -0600 [thread overview]
Message-ID: <167033218290.236219.3964235132732494862.robh@kernel.org> (raw)
In-Reply-To: <20221206073916.1606125-2-jk@codeconstruct.com.au>
On Tue, 06 Dec 2022 15:39:15 +0800, Jeremy Kerr wrote:
> Simple syscon devices may require deassertion of a reset signal in order
> to access their register set. This change adds the `resets` property from
> reset.yaml#/properties/resets (referenced through core.yaml), specifying
> a maxItems of 1 for a single (optional) reset descriptor.
>
> This will allow a future change to the syscon driver to implement reset
> control.
>
> Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
> ---
> Documentation/devicetree/bindings/mfd/syscon.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-12-06 13:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 7:39 [RFC PATCH 0/2] Add reset control for mfd syscon devices Jeremy Kerr
2022-12-06 7:39 ` [RFC PATCH 1/2] dt-bindings: mfd/syscon: Add resets property Jeremy Kerr
2022-12-06 13:09 ` Rob Herring [this message]
2022-12-06 7:39 ` [RFC PATCH 2/2] mfd: syscon: allow reset control for syscon devices Jeremy Kerr
2022-12-06 8:41 ` Arnd Bergmann
2022-12-06 9:25 ` Philipp Zabel
2022-12-06 14:18 ` Arnd Bergmann
2022-12-07 7:56 ` Jeremy Kerr
2022-12-07 8:59 ` Arnd Bergmann
2022-12-07 9:28 ` Jeremy Kerr
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=167033218290.236219.3964235132732494862.robh@kernel.org \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=jk@codeconstruct.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®