From: Philipp Zabel <p.zabel@pengutronix.de>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Jassi Brar <jaswinder.singh@linaro.org>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] reset: uniphier: fix USB clock line for LD20
Date: Fri, 27 Apr 2018 12:04:02 +0200 [thread overview]
Message-ID: <1524823442.17614.2.camel@pengutronix.de> (raw)
In-Reply-To: <CAK7LNAQKVD3aKTo_z=zkOdoL--RogoFm0bt-dCBsWFN8BEPpSg@mail.gmail.com>
On Fri, 2018-04-27 at 18:42 +0900, Masahiro Yamada wrote:
> Philipp,
>
> 2018-04-12 11:16 GMT+09:00 Masahiro Yamada <yamada.masahiro@socionext.com>:
> > For LD20, the bit 5 of the offset 0x200c turned out to be a USB3
> > reset. The hardware document says it is the GIO reset despite LD20
> > has no GIO bus, confusingly.
> >
> > Also, fix confusing comments for PXs3.
> >
> > Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> > ---
>
> Can you take a look at this, please?
Thank you for the reminder, I've applied it to reset/fixes and rebased
reset/next on top to include it.
regards
Philipp
WARNING: multiple messages have this Message-ID (diff)
From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] reset: uniphier: fix USB clock line for LD20
Date: Fri, 27 Apr 2018 12:04:02 +0200 [thread overview]
Message-ID: <1524823442.17614.2.camel@pengutronix.de> (raw)
In-Reply-To: <CAK7LNAQKVD3aKTo_z=zkOdoL--RogoFm0bt-dCBsWFN8BEPpSg@mail.gmail.com>
On Fri, 2018-04-27 at 18:42 +0900, Masahiro Yamada wrote:
> Philipp,
>
> 2018-04-12 11:16 GMT+09:00 Masahiro Yamada <yamada.masahiro@socionext.com>:
> > For LD20, the bit 5 of the offset 0x200c turned out to be a USB3
> > reset. The hardware document says it is the GIO reset despite LD20
> > has no GIO bus, confusingly.
> >
> > Also, fix confusing comments for PXs3.
> >
> > Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> > ---
>
> Can you take a look at this, please?
Thank you for the reminder, I've applied it to reset/fixes and rebased
reset/next on top to include it.
regards
Philipp
next prev parent reply other threads:[~2018-04-27 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 2:16 [PATCH] reset: uniphier: fix USB clock line for LD20 Masahiro Yamada
2018-04-12 2:16 ` Masahiro Yamada
2018-04-27 9:42 ` Masahiro Yamada
2018-04-27 9:42 ` Masahiro Yamada
2018-04-27 10:04 ` Philipp Zabel [this message]
2018-04-27 10:04 ` 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=1524823442.17614.2.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=hayashi.kunihiko@socionext.com \
--cc=jaswinder.singh@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=yamada.masahiro@socionext.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 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.