From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: OMAP3+: VP: collate fixes
Date: Fri, 18 May 2012 14:33:18 -0500 [thread overview]
Message-ID: <1337369601-14915-1-git-send-email-nm@ti.com> (raw)
In-Reply-To: <[PATCH] ARM: OMAP3+: PM: VP: ensure VP is idle before disable>
Reviewing the android code base brought out a few fixes that upstream
does not have, so collating them and posting them out in this chain.
Nishanth Menon (2):
ARM: OMAP3+: PM: VP: check to ensure VP is idle before forceupdate
ARM: OMAP3+: PM: VP: check only the VPINIDLE status bit
Wenbiao Wang (1):
ARM: OMAP3+: PM: VP: ensure VP is idle before disable
arch/arm/mach-omap2/vp.c | 34 ++++++++++++++++++++++++++++++----
arch/arm/mach-omap2/vp.h | 3 ++-
arch/arm/mach-omap2/vp3xxx_data.c | 1 +
arch/arm/mach-omap2/vp44xx_data.c | 1 +
4 files changed, 34 insertions(+), 5 deletions(-)
Cc: Tony Lindgren <tony@atomide.com>
Cc: Kevin Hilman <khilman@ti.com>
Cc: linux-omap at vger.kernel.org
Cc: linux-arm-kernel at lists.infradead.org
Regards,
Nishanth Menon
--
1.7.9.5
next prev parent reply other threads:[~2012-05-18 19:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH] ARM: OMAP3+: PM: VP: ensure VP is idle before disable>
2012-05-18 18:18 ` [PATCH V2] ARM: OMAP3+: PM: VP: ensure VP is idle before disable Nishanth Menon
2012-05-19 9:52 ` Eduardo Valentin
2012-05-21 13:36 ` Menon, Nishanth
2012-05-21 14:51 ` Eduardo Valentin
2012-05-21 15:14 ` Menon, Nishanth
2012-05-22 7:02 ` Valentin, Eduardo
2012-05-18 19:33 ` Nishanth Menon [this message]
2012-05-18 19:33 ` [PATCH 1/3] " Nishanth Menon
2012-05-31 23:21 ` Kevin Hilman
2012-05-31 23:28 ` Kevin Hilman
2012-05-31 23:35 ` Nishanth Menon
2012-05-18 19:33 ` [PATCH 2/3] ARM: OMAP3+: PM: VP: check to ensure VP is idle before forceupdate Nishanth Menon
2012-05-31 23:23 ` Kevin Hilman
2012-05-31 23:37 ` Nishanth Menon
2012-05-18 19:33 ` [PATCH 3/3] ARM: OMAP3+: PM: VP: check only the VPINIDLE status bit Nishanth Menon
2012-05-31 23:27 ` Kevin Hilman
2012-05-31 23:39 ` Nishanth Menon
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=1337369601-14915-1-git-send-email-nm@ti.com \
--to=nm@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).