From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: Vignesh R <vigneshr@ti.com>, Rob Herring <robh+dt@kernel.org>,
Russell King <linux@arm.linux.org.uk>,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: dra72-evm: Mark uart1 rxd as wakeup capable
Date: Mon, 30 Nov 2015 13:56:52 -0800 [thread overview]
Message-ID: <20151130215652.GF23396@atomide.com> (raw)
In-Reply-To: <5657E3DE.5000107@ti.com>
* Nishanth Menon <nm@ti.com> [151126 21:03]:
> On 11/26/2015 02:31 AM, Vignesh R wrote:
> > Uart1 rxd is wakeup capable on DRA72 EVM. Hence, mark rxd line as
> > wakeup capable. This is similar to commit 66b0436977e2c ("ARM: dts:
> > dra7-evm: Mark uart1 rxd as wakeup capable") for DRA74 EVM.
> >
> > Signed-off-by: Vignesh R <vigneshr@ti.com>
> > ---
> > arch/arm/boot/dts/dra72-evm.dts | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/dra72-evm.dts b/arch/arm/boot/dts/dra72-evm.dts
> > index d6104d5f0c01..8bf36b0b3c33 100644
> > --- a/arch/arm/boot/dts/dra72-evm.dts
> > +++ b/arch/arm/boot/dts/dra72-evm.dts
> > @@ -478,6 +478,8 @@
> >
> > &uart1 {
> > status = "okay";
> > + interrupts-extended = <&crossbar_mpu GIC_SPI 67 IRQ_TYPE_LEVEL_HIGH>,
> > + <&dra7_pmx_core 0x3e0>;
> > };
> >
> > &elm {
> >
>
> Acked-by: Nishanth Menon <nm@ti.com>
Applying into omap-for-v4.5/dt thanks.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: dra72-evm: Mark uart1 rxd as wakeup capable
Date: Mon, 30 Nov 2015 13:56:52 -0800 [thread overview]
Message-ID: <20151130215652.GF23396@atomide.com> (raw)
In-Reply-To: <5657E3DE.5000107@ti.com>
* Nishanth Menon <nm@ti.com> [151126 21:03]:
> On 11/26/2015 02:31 AM, Vignesh R wrote:
> > Uart1 rxd is wakeup capable on DRA72 EVM. Hence, mark rxd line as
> > wakeup capable. This is similar to commit 66b0436977e2c ("ARM: dts:
> > dra7-evm: Mark uart1 rxd as wakeup capable") for DRA74 EVM.
> >
> > Signed-off-by: Vignesh R <vigneshr@ti.com>
> > ---
> > arch/arm/boot/dts/dra72-evm.dts | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/dra72-evm.dts b/arch/arm/boot/dts/dra72-evm.dts
> > index d6104d5f0c01..8bf36b0b3c33 100644
> > --- a/arch/arm/boot/dts/dra72-evm.dts
> > +++ b/arch/arm/boot/dts/dra72-evm.dts
> > @@ -478,6 +478,8 @@
> >
> > &uart1 {
> > status = "okay";
> > + interrupts-extended = <&crossbar_mpu GIC_SPI 67 IRQ_TYPE_LEVEL_HIGH>,
> > + <&dra7_pmx_core 0x3e0>;
> > };
> >
> > &elm {
> >
>
> Acked-by: Nishanth Menon <nm@ti.com>
Applying into omap-for-v4.5/dt thanks.
Tony
next prev parent reply other threads:[~2015-11-30 21:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 8:31 [PATCH] ARM: dts: dra72-evm: Mark uart1 rxd as wakeup capable Vignesh R
2015-11-26 8:31 ` Vignesh R
2015-11-26 8:31 ` Vignesh R
2015-11-27 5:02 ` Nishanth Menon
2015-11-27 5:02 ` Nishanth Menon
2015-11-27 5:02 ` Nishanth Menon
2015-11-30 21:56 ` Tony Lindgren [this message]
2015-11-30 21:56 ` Tony Lindgren
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=20151130215652.GF23396@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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.