devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: "Tony Lindgren" <tony@atomide.com>,
	"Benoît Cousson" <bcousson@baylibre.com>
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-omap@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: omap5-uevm: Add Uart wakeup interrupt
Date: Fri, 15 May 2015 17:01:46 -0500	[thread overview]
Message-ID: <55566CCA.5070701@ti.com> (raw)
In-Reply-To: <1431727161-16870-1-git-send-email-nm@ti.com>

On 05/15/2015 04:59 PM, Nishanth Menon wrote:
> UART3 wakeup takes place with iodaisy chain. enable the wakeup pin.
> 
> Reported-by: Suman Anna <s-anna@ti.com>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> 
> Test on linus master (f0897f4cc0fc) with 8250  driver: http://pastebin.ubuntu.com/11154446/
> 
> Applies on next-20150515 and linus master (f0897f4cc0fc)
> 
>  arch/arm/boot/dts/omap5-uevm.dts |    2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/arm/boot/dts/omap5-uevm.dts b/arch/arm/boot/dts/omap5-uevm.dts
> index 74777a6e200a..214190796143 100644
> --- a/arch/arm/boot/dts/omap5-uevm.dts
> +++ b/arch/arm/boot/dts/omap5-uevm.dts
> @@ -604,6 +604,8 @@
>  &uart3 {
>          pinctrl-names = "default";
>          pinctrl-0 = <&uart3_pins>;
> +	interrupts-extended = <&gic GIC_SPI 74 IRQ_TYPE_LEVEL_HIGH>,
I think I should have used WUGEN here! Sorry about that.. just noticed
in the log
308:        259          0       GIC 106 Level     serial

Sorry about that.
> +			      <&omap5_pmx_core 0x19c>;
>  };
>  
>  &uart5 {
> 


-- 
Regards,
Nishanth Menon

      reply	other threads:[~2015-05-15 22:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 21:59 [PATCH] ARM: dts: omap5-uevm: Add Uart wakeup interrupt Nishanth Menon
2015-05-15 22:01 ` Nishanth Menon [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=55566CCA.5070701@ti.com \
    --to=nm@ti.com \
    --cc=bcousson@baylibre.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=tony@atomide.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).