From: Tero Kristo <t-kristo@ti.com>
To: Tony Lindgren <tony@atomide.com>, Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org
Subject: Re: OMAP baseline test results for v3.16-rc4
Date: Thu, 31 Jul 2014 16:12:03 +0300 [thread overview]
Message-ID: <53DA40A3.30102@ti.com> (raw)
In-Reply-To: <20140730053940.GX29045@atomide.com>
On 07/30/2014 08:39 AM, Tony Lindgren wrote:
> 8< -----------------------------------
> From: Tony Lindgren<tony@atomide.com>
> Date: Tue, 29 Jul 2014 22:36:59 -0700
> Subject: [PATCH] ARM: dts: Enable UART wake-up events for beagleboard
>
> For device tree based booting, we need to use wake-up
> interrupts like we already do for some omaps. This fixes
> a PM regression on beagleboard compared to legacy booting.
>
> Signed-off-by: Tony Lindgren<tony@atomide.com>
>
> --- a/arch/arm/boot/dts/omap3-beagle.dts
> +++ b/arch/arm/boot/dts/omap3-beagle.dts
> @@ -292,6 +292,7 @@
> &uart3 {
> pinctrl-names = "default";
> pinctrl-0 = <&uart3_pins>;
> + interrupts-extended = <&intc 74 &omap3_pmx_core OMAP3_UART3_RX>;
> };
>
> &gpio1 {
> --
The above patch works for me with ret/off-idle on beagle rev C4 on top
of 3.16-rc5. Without it, the board just seems to hang with ret, and with
off, it just doesn't respond to anything on uart but seems alive otherwise.
Tested-by: Tero Kristo <t-kristo@ti.com>
next prev parent reply other threads:[~2014-07-31 13:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-06 23:41 OMAP baseline test results for v3.16-rc4 Paul Walmsley
2014-07-07 8:02 ` Tony Lindgren
2014-07-14 17:28 ` Paul Walmsley
2014-07-15 6:04 ` Tony Lindgren
2014-07-15 19:56 ` Paul Walmsley
2014-07-25 19:14 ` Paul Walmsley
2014-07-29 6:42 ` Tony Lindgren
2014-07-29 8:25 ` Paul Walmsley
2014-07-29 8:49 ` Tony Lindgren
2014-07-29 12:32 ` Paul Walmsley
2014-07-29 12:57 ` Paul Walmsley
2014-07-29 14:53 ` Tony Lindgren
2014-07-29 19:37 ` Paul Walmsley
2014-07-30 5:39 ` Tony Lindgren
2014-07-30 7:53 ` Paul Walmsley
2014-07-31 13:11 ` Tony Lindgren
2014-07-31 19:27 ` Paul Walmsley
2014-08-01 7:10 ` Tony Lindgren
2014-08-01 7:52 ` Tony Lindgren
2014-08-07 22:21 ` Paul Walmsley
2014-08-08 2:14 ` Felipe Balbi
2014-08-08 6:11 ` Paul Walmsley
2014-08-08 14:34 ` Felipe Balbi
2014-08-08 23:39 ` Paul Walmsley
2014-08-09 2:49 ` Felipe Balbi
2014-08-08 2:29 ` Fabio Estevam
2014-08-08 6:14 ` Paul Walmsley
2014-08-09 12:41 ` Ezequiel Garcia
2014-07-31 13:12 ` Tero Kristo [this message]
2014-07-29 8:50 ` Paul Walmsley
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=53DA40A3.30102@ti.com \
--to=t-kristo@ti.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--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).