devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] arm64: dts: r8a7796: add IMR-LX4 support
Date: Wed, 5 Jul 2017 11:42:26 +0100	[thread overview]
Message-ID: <20170705104225.GD24043@verge.net.au> (raw)
In-Reply-To: <CAMuHMdXxcbkPV+Jt7Xo5emQ4fyDHm1p1RgD9nsRfR78va4XFSA@mail.gmail.com>

On Wed, Jul 05, 2017 at 11:54:20AM +0200, Geert Uytterhoeven wrote:
> Hi Sergei,
> 
> On Tue, Jun 27, 2017 at 7:33 PM, Sergei Shtylyov
> <sergei.shtylyov@cogentembedded.com> wrote:
> > Describe the IMR-LX4 devices in the R8A7796 device tree.
> >
> > Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
> 
> > --- renesas.orig/arch/arm64/boot/dts/renesas/r8a7796.dtsi
> > +++ renesas/arch/arm64/boot/dts/renesas/r8a7796.dtsi
> > @@ -1454,5 +1454,23 @@
> >                                 };
> >                         };
> >                 };
> > +
> > +               imr-lx4@fe860000 {
> > +                       compatible = "renesas,r8a7796-imr-lx4",
> > +                                    "renesas,imr-lx4";
> > +                       reg = <0 0xfe860000 0 0x2000>;
> > +                       interrupts = <GIC_SPI 192 IRQ_TYPE_LEVEL_HIGH>;
> > +                       clocks = <&cpg CPG_MOD 823>;
> > +                       power-domains = <&sysc R8A7796_PD_A3VC>;
> 
> resets = <&cpg 823>;
> 
> > +               };
> > +
> > +               imr-lx4@fe870000 {
> > +                       compatible = "renesas,r8a7796-imr-lx4",
> > +                                    "renesas,imr-lx4";
> > +                       reg = <0 0xfe870000 0 0x2000>;
> > +                       interrupts = <GIC_SPI 193 IRQ_TYPE_LEVEL_HIGH>;
> > +                       clocks = <&cpg CPG_MOD 822>;
> > +                       power-domains = <&sysc R8A7796_PD_A3VC>;
> 
> resets = <&cpg 822>;
> 
> With the issues above fixed:
> 
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>

Thanks, fixed.

  reply	other threads:[~2017-07-05 10:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-27 17:33 [PATCH v2] arm64: dts: r8a7796: add IMR-LX4 support Sergei Shtylyov
     [not found] ` <20170627173400.581660959-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2017-06-30  9:56   ` Simon Horman
2017-07-05  9:54 ` Geert Uytterhoeven
2017-07-05 10:42   ` Simon Horman [this message]
2017-07-05 12:03   ` Sergei Shtylyov
2017-07-05 13:04     ` Simon Horman

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=20170705104225.GD24043@verge.net.au \
    --to=horms@verge.net.au \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=will.deacon@arm.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).