From: Masahiro Yamada <masahiroy@kernel.org>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Jassi Brar <jaswinder.singh@linaro.org>,
Masami Hiramatsu <masami.hiramatsu@linaro.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] reset: uniphier: Add SCSSI reset control for each channel
Date: Tue, 3 Dec 2019 15:40:11 +0900 [thread overview]
Message-ID: <CAK7LNAQvsw-bgXm5u-z0gtSZ078RvPFU10yqyhBRi2Oaq4bqdA@mail.gmail.com> (raw)
In-Reply-To: <20191203151149.52A8.4A936039@socionext.com>
On Tue, Dec 3, 2019 at 3:14 PM Kunihiko Hayashi
<hayashi.kunihiko@socionext.com> wrote:
>
> Hi Philipp,
>
> On Mon, 2 Dec 2019 14:06:20 +0100 <p.zabel@pengutronix.de> wrote:
>
> > On Fri, 2019-11-29 at 13:19 +0900, Kunihiko Hayashi wrote:
> > > SCSSI has reset controls for each channel in the SoCs newer than Pro4,
> > > so this adds missing reset controls for channel 1, 2 and 3. And more, this
> > > moves MCSSI reset ID after SCSSI.
> >
> > Just to be sure, there are no device trees in circulation that already
> > use the MCSSI reset?
>
> Yes, currently no device trees refer to MCSSI reset,
> so I think MCSSI reset ID can be moved.
>
> Thank you,
>
> ---
> Best Regards,
> Kunihiko Hayashi
>
Fixes: 6b39fd590aeb ("reset: uniphier: add reset control support for SPI")
Assuming you tested it this time,
Acked-by: Masahiro Yamada <yamada.masahiro@socionext.com>
--
Best Regards
Masahiro Yamada
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-03 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 4:19 [PATCH] reset: uniphier: Add SCSSI reset control for each channel Kunihiko Hayashi
2019-12-02 13:06 ` Philipp Zabel
2019-12-03 6:11 ` Kunihiko Hayashi
2019-12-03 6:40 ` Masahiro Yamada [this message]
2019-12-03 14:01 ` Philipp Zabel
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=CAK7LNAQvsw-bgXm5u-z0gtSZ078RvPFU10yqyhBRi2Oaq4bqdA@mail.gmail.com \
--to=masahiroy@kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu@linaro.org \
--cc=p.zabel@pengutronix.de \
/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).