devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Yang <leoyang.li@nxp.com>
To: Shawn Guo <shawnguo@kernel.org>
Cc: kurt@linutronix.de, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: ls208xa: add second duart
Date: Sun, 2 Sep 2018 21:40:56 -0500	[thread overview]
Message-ID: <CADRPPNRf8Hzu7FZoSERZLy=jX4c1RG0b3DJuMYhYLw6HjgdsPA@mail.gmail.com> (raw)
In-Reply-To: <20180903023120.GG3850@dragon>

On Sun, Sep 2, 2018 at 9:34 PM Shawn Guo <shawnguo@kernel.org> wrote:
>
> It looks good to me.  @Leo, are you okay with it?

It looks fine.

Acked-by: Li Yang <leoyang.li@nxp.com>

>
> Shawn
>
> On Thu, Aug 30, 2018 at 11:00:38AM +0200, Kurt Kanzenbach wrote:
> > The NXP LS208xA SoCs have two dual uarts. Thus, add the second one.
> >
> > Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de>
> > ---
> >  arch/arm64/boot/dts/freescale/fsl-ls208xa.dtsi | 16 ++++++++++++++++
> >  1 file changed, 16 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/freescale/fsl-ls208xa.dtsi b/arch/arm64/boot/dts/freescale/fsl-ls208xa.dtsi
> > index 8cb78dd99672..547a86ec7cd2 100644
> > --- a/arch/arm64/boot/dts/freescale/fsl-ls208xa.dtsi
> > +++ b/arch/arm64/boot/dts/freescale/fsl-ls208xa.dtsi
> > @@ -22,6 +22,8 @@
> >               crypto = &crypto;
> >               serial0 = &serial0;
> >               serial1 = &serial1;
> > +             serial2 = &serial2;
> > +             serial3 = &serial3;
> >       };
> >
> >       cpu: cpus {
> > @@ -221,6 +223,20 @@
> >                       interrupts = <0 32 0x4>; /* Level high type */
> >               };
> >
> > +             serial2: serial@21d0500 {
> > +                     compatible = "fsl,ns16550", "ns16550a";
> > +                     reg = <0x0 0x21d0500 0x0 0x100>;
> > +                     clocks = <&clockgen 4 3>;
> > +                     interrupts = <0 33 0x4>; /* Level high type */
> > +             };
> > +
> > +             serial3: serial@21d0600 {
> > +                     compatible = "fsl,ns16550", "ns16550a";
> > +                     reg = <0x0 0x21d0600 0x0 0x100>;
> > +                     clocks = <&clockgen 4 3>;
> > +                     interrupts = <0 33 0x4>; /* Level high type */
> > +             };
> > +
> >               cluster1_core0_watchdog: wdt@c000000 {
> >                       compatible = "arm,sp805-wdt", "arm,primecell";
> >                       reg = <0x0 0xc000000 0x0 0x1000>;
> > --
> > 2.11.0
> >

  reply	other threads:[~2018-09-03  2:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30  9:00 [PATCH] arm64: dts: ls208xa: add second duart Kurt Kanzenbach
2018-09-03  2:31 ` Shawn Guo
2018-09-03  2:40   ` Li Yang [this message]
2018-09-03  2:47 ` Shawn Guo

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='CADRPPNRf8Hzu7FZoSERZLy=jX4c1RG0b3DJuMYhYLw6HjgdsPA@mail.gmail.com' \
    --to=leoyang.li@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kurt@linutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@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).