From: Philipp Zabel <p.zabel@pengutronix.de>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Rob Herring <robh+dt@kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] reset: uniphier: Introduce some features and NX1 support
Date: Tue, 05 Oct 2021 11:59:07 +0200 [thread overview]
Message-ID: <0cf9a2bd61bf688ea94abf6d463e80b46b1495cc.camel@pengutronix.de> (raw)
In-Reply-To: <1633399842-1402-1-git-send-email-hayashi.kunihiko@socionext.com>
On Tue, 2021-10-05 at 11:10 +0900, Kunihiko Hayashi wrote:
> This series includes the patches to add audio/video reset lines for PXs3 SoC
> and basic reset lines for new UniPhier NX1 SoC. NX1 SoC also has the same
> kinds of reset lines as the other UniPhier SoCs.
>
> Kunihiko Hayashi (3):
> reset: uniphier: Add audio system and video input reset control for
> PXs3
> dt-bindings: reset: uniphier: Add NX1 reset control binding
> reset: uniphier: Add NX1 reset support
>
> .../reset/socionext,uniphier-glue-reset.yaml | 1 +
> .../bindings/reset/socionext,uniphier-reset.yaml | 3 +++
> drivers/reset/reset-uniphier-glue.c | 4 ++++
> drivers/reset/reset-uniphier.c | 27 ++++++++++++++++++++++
> 4 files changed, 35 insertions(+)
Thank you, applied to reset/next.
regards
Philipp
prev parent reply other threads:[~2021-10-05 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 2:10 [PATCH 0/3] reset: uniphier: Introduce some features and NX1 support Kunihiko Hayashi
2021-10-05 2:10 ` [PATCH 1/3] reset: uniphier: Add audio system and video input reset control for PXs3 Kunihiko Hayashi
2021-10-05 2:10 ` [PATCH 2/3] dt-bindings: reset: uniphier: Add NX1 reset control binding Kunihiko Hayashi
2021-10-05 12:26 ` Rob Herring
2021-10-05 2:10 ` [PATCH 3/3] reset: uniphier: Add NX1 reset support Kunihiko Hayashi
2021-10-05 9:59 ` Philipp Zabel [this message]
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=0cf9a2bd61bf688ea94abf6d463e80b46b1495cc.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).