From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v10 04/07] arm64: renesas: r8a7795 dtsi: Add all SCIF nodes
Date: Mon, 05 Oct 2015 02:30:05 +0000 [thread overview]
Message-ID: <20151005023005.GH25427@verge.net.au> (raw)
In-Reply-To: <20151002025551.28158.20307.sendpatchset@little-apple>
On Fri, Oct 02, 2015 at 10:13:02AM +0200, Geert Uytterhoeven wrote:
> Hi Simon,
>
> On Fri, Oct 2, 2015 at 10:08 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Fri, Oct 02, 2015 at 09:11:50AM +0200, Geert Uytterhoeven wrote:
> >> On Fri, Oct 2, 2015 at 4:55 AM, Magnus Damm <magnus.damm@gmail.com> wrote:
> >> > --- 0012/include/dt-bindings/clock/r8a7795-clock.h
> >> > +++ work/include/dt-bindings/clock/r8a7795-clock.h 2015-10-01 19:24:51.200513000 +0900
> >> > @@ -22,8 +22,14 @@
> >> > /* MSTP1 */
> >> >
> >> > /* MSTP2 */
> >> > +#define R8A7795_CLK_SCIF5 202
> >> > +#define R8A7795_CLK_SCIF4 203
> >> > +#define R8A7795_CLK_SCIF3 204
> >> > +#define R8A7795_CLK_SCIF1 206
> >> > +#define R8A7795_CLK_SCIF0 207
> >> >
> >> > /* MSTP3 */
> >> > +#define R8A7795_CLK_SCIF2 210
> >>
> >> 310
> >
> > Thanks, I will fix that.
> >
> > I plan to wait a little to accumulate more changes.
> > But if for some reason you need this in a hurry I can
> > push an updated topic branch ASAP.
>
> Given how close we are to leaving for ELCE, I think we can live with it.
As I am rebasing other branches I have pushed the above in
topic/arm64-rcar-gen3-v10.1.
> The correct clock will have been enabled by the boot loader anyway.
> MSTP210 is MSIOF1, so no animals will be hurt by accidentally touching that
> clock.
:)
prev parent reply other threads:[~2015-10-05 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 2:55 [PATCH v10 04/07] arm64: renesas: r8a7795 dtsi: Add all SCIF nodes Magnus Damm
2015-10-02 7:11 ` Geert Uytterhoeven
2015-10-02 8:08 ` Simon Horman
2015-10-02 8:13 ` Geert Uytterhoeven
2015-10-05 2:30 ` Simon Horman [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=20151005023005.GH25427@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.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).