From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 0/4] ARM: OMAP3+: VP: collate fixes
Date: Thu, 31 May 2012 20:41:35 -0500 [thread overview]
Message-ID: <1338514899-3560-1-git-send-email-nm@ti.com> (raw)
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 (3):
ARM: OMAP3+: PM: VP: check only the VPINIDLE status bit
ARM: OMAP3+: PM: VP: move check of idle to separate function
ARM: OMAP3+: PM: VP: check to ensure VP is idle before forceupdate
Wenbiao Wang (1):
ARM: OMAP3+: PM: VP: ensure VP is idle before disable
arch/arm/mach-omap2/vp.c | 65 +++++++++++++++++++++++++++++++------
arch/arm/mach-omap2/vp.h | 10 ++++--
arch/arm/mach-omap2/vp3xxx_data.c | 1 +
arch/arm/mach-omap2/vp44xx_data.c | 1 +
4 files changed, 65 insertions(+), 12 deletions(-)
Changes in v4:
vp idle moved off to a seperate function
reordered patches to reduce loc changes
rate controlled warnings
Previous revs:
V1: http://marc.info/?l=linux-omap&m=133736976423629&w=2
Cc: Tony Lindgren <tony@atomide.com>
Cc: Kevin Hilman <khilman@ti.com>
--
Regards,
Nishanth Menon
--
1.7.9.5
next reply other threads:[~2012-06-01 1:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 1:41 Nishanth Menon [this message]
2012-06-01 1:41 ` [PATCH V2 1/4] ARM: OMAP3+: PM: VP: check only the VPINIDLE status bit Nishanth Menon
2012-06-01 1:41 ` [PATCH V2 2/4] ARM: OMAP3+: PM: VP: move check of idle to separate function Nishanth Menon
2012-06-01 21:07 ` Kevin Hilman
2012-06-01 1:41 ` [PATCH V2 3/4] ARM: OMAP3+: PM: VP: check to ensure VP is idle before forceupdate Nishanth Menon
2012-06-01 21:08 ` Kevin Hilman
2012-06-01 1:41 ` [PATCH V2 4/4] ARM: OMAP3+: PM: VP: ensure VP is idle before disable Nishanth Menon
2012-06-01 21:03 ` Kevin Hilman
2012-06-01 22:57 ` Menon, Nishanth
2012-06-04 16:49 ` 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=1338514899-3560-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).