From: Kevin Hilman <khilman@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
santosh.shilimkar@ti.com, rnayak@ti.com
Subject: Re: [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4
Date: Thu, 02 Feb 2012 10:38:31 -0800 [thread overview]
Message-ID: <87ty39cc7s.fsf@ti.com> (raw)
In-Reply-To: <20120202093600.12509.35052.stgit@dusk> (Paul Walmsley's message of "Thu, 02 Feb 2012 02:38:48 -0700")
Paul Walmsley <paul@pwsan.com> writes:
> Hi
>
> This series consolidates some duplicated PM code across OMAP2, 3, and 4.
> This saves both binary kernel image size, and lines of source. These
> functions are just the low-hanging fruit; it looks to me like there's even
> more consolidation that could be done.
>
> Suspend + UART wakeup was tested on OMAP44xx BeagleBoard.
I assume you meant Panda board?
> On the OMAP35xx Beagleboard here, v3.3-rc2 doesn't seem to wake up
> from suspend correctly with or without these patches, so I've only
> boot-tested them on that platform.
I also tested idle & suspend + UART wakeup on 3430/n900, 3530/Overo.
Will add these to my cleanup queue for v3.4[1] after adding a Tested-by
from Santosh.
Kevin
[1]
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.4/cleanup/pm
WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4
Date: Thu, 02 Feb 2012 10:38:31 -0800 [thread overview]
Message-ID: <87ty39cc7s.fsf@ti.com> (raw)
In-Reply-To: <20120202093600.12509.35052.stgit@dusk> (Paul Walmsley's message of "Thu, 02 Feb 2012 02:38:48 -0700")
Paul Walmsley <paul@pwsan.com> writes:
> Hi
>
> This series consolidates some duplicated PM code across OMAP2, 3, and 4.
> This saves both binary kernel image size, and lines of source. These
> functions are just the low-hanging fruit; it looks to me like there's even
> more consolidation that could be done.
>
> Suspend + UART wakeup was tested on OMAP44xx BeagleBoard.
I assume you meant Panda board?
> On the OMAP35xx Beagleboard here, v3.3-rc2 doesn't seem to wake up
> from suspend correctly with or without these patches, so I've only
> boot-tested them on that platform.
I also tested idle & suspend + UART wakeup on 3430/n900, 3530/Overo.
Will add these to my cleanup queue for v3.4[1] after adding a Tested-by
from Santosh.
Kevin
[1]
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.4/cleanup/pm
next prev parent reply other threads:[~2012-02-02 18:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 9:38 [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4 Paul Walmsley
2012-02-02 9:38 ` Paul Walmsley
2012-02-02 9:38 ` [PATCH 1/2] ARM: OMAP2+: PM: share clkdms_setup() across OMAP2, 3, 4 Paul Walmsley
2012-02-02 9:38 ` Paul Walmsley
2012-02-02 9:38 ` [PATCH 2/2] ARM: OMAP2+: PM: share some suspend-related functions " Paul Walmsley
2012-02-02 9:38 ` Paul Walmsley
2012-02-02 11:25 ` [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4 Shilimkar, Santosh
2012-02-02 11:25 ` Shilimkar, Santosh
2012-02-02 18:38 ` Kevin Hilman [this message]
2012-02-02 18:38 ` Kevin Hilman
2012-02-02 18:40 ` Paul Walmsley
2012-02-02 18:40 ` Paul Walmsley
2012-02-02 20:29 ` Paul Walmsley
2012-02-02 20:29 ` Paul Walmsley
2012-03-08 12:21 ` Coelho, Luciano
2012-03-08 12:21 ` Coelho, Luciano
2012-03-08 18:18 ` Paul Walmsley
2012-03-08 18:18 ` Paul Walmsley
2012-03-08 18:27 ` Kevin Hilman
2012-03-08 18:27 ` Kevin Hilman
2012-03-08 18:47 ` Luciano Coelho
2012-03-08 18:47 ` Luciano Coelho
2012-03-08 18:55 ` Paul Walmsley
2012-03-08 18:55 ` Paul Walmsley
2012-03-08 19:05 ` Luciano Coelho
2012-03-08 19:05 ` Luciano Coelho
2012-03-08 21:21 ` Kevin Hilman
2012-03-08 21:21 ` Kevin Hilman
2012-03-09 6:15 ` Luciano Coelho
2012-03-09 6:15 ` Luciano Coelho
2012-03-09 15:23 ` Kevin Hilman
2012-03-09 15:23 ` Kevin Hilman
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=87ty39cc7s.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@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.