From: Rob Herring <robh@kernel.org>
To: Steen Hegelund <steen.hegelund@microchip.com>
Cc: Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org,
Gregory Clement <gregory.clement@bootlin.com>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
devicetree@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-arm-kernel@lists.infradead.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH v8 1/3] dt-bindings: reset: microchip sparx5 reset driver bindings
Date: Tue, 23 Mar 2021 16:07:40 -0600 [thread overview]
Message-ID: <20210323220740.GA1425527@robh.at.kernel.org> (raw)
In-Reply-To: <20210316090839.3207930-2-steen.hegelund@microchip.com>
On Tue, 16 Mar 2021 10:08:37 +0100, Steen Hegelund wrote:
> Document the Sparx5 reset device driver bindings
>
> The driver uses a syscon and an IO range on sparx5 for access to
> the reset control and the reset status.
>
> Sparx5 will no longer use the existing Ocelot chip reset driver, but use
> this new switch reset driver as it has the reset controller interface that
> allows the first client to perform the reset on behalf of all the Sparx5
> component drivers.
>
> Signed-off-by: Steen Hegelund <steen.hegelund@microchip.com>
> ---
> .../bindings/reset/microchip,rst.yaml | 58 +++++++++++++++++++
> 1 file changed, 58 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/reset/microchip,rst.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-03-23 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210316090839.3207930-1-steen.hegelund@microchip.com>
2021-03-16 9:08 ` [PATCH v8 1/3] dt-bindings: reset: microchip sparx5 reset driver bindings Steen Hegelund
2021-03-23 22:07 ` Rob Herring [this message]
2021-03-16 9:08 ` [PATCH v8 3/3] arm64: dts: reset: add microchip sparx5 switch reset driver Steen Hegelund
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=20210323220740.GA1425527@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=steen.hegelund@microchip.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).