From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/5] Convert I2C driver to use omap_device/runtime PM
Date: Mon, 27 Sep 2010 13:02:47 -0700 [thread overview]
Message-ID: <87vd5rnee0.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1285078036-12789-1-git-send-email-rnayak@ti.com> (Rajendra Nayak's message of "Tue, 21 Sep 2010 19:37:11 +0530")
Ben,
Rajendra Nayak <rnayak@ti.com> writes:
> This series makes I2C device registration use hwmod and omap_device api's
> and converts the I2C driver to use runtime PM api's.
>
> Patches apply on the pm-core branch from Kevin's tree.
If you're OK with the driver changes in PATCH 5/5, with your Ack, we can
queue this via the OMAP tree with all the platform changes that it
depends on.
Thanks,
Kevin
> v3 has minor review comment fixes over v2
> The series is boot tested on a 2430sdp platform along with being tested
> on 3430sdp and 4430sdp.
>
> 4430sdp tests are done using the below series
> http://www.spinics.net/lists/linux-omap/msg36023.html
>
> Paul Walmsley (2):
> OMAP2xxx: hwmod: add I2C hwmods for OMAP2420, 2430
> OMAP: I2C: split device registration and convert OMAP2+ to
> omap_device
>
> Rajendra Nayak (3):
> OMAP3: hwmod: add I2C hwmods for OMAP3430
> OMAP4: hwmod: add I2C hwmods for OMAP4430
> OMAP: I2C: Convert i2c driver to use PM runtime api's
>
> arch/arm/mach-omap2/cm-regbits-24xx.h | 4 +
> arch/arm/mach-omap2/omap_hwmod_2420_data.c | 140 ++++++++++++++++-
> arch/arm/mach-omap2/omap_hwmod_2430_data.c | 154 ++++++++++++++++++-
> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 232 +++++++++++++++++++++++++++
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 237 ++++++++++++++++++++++++++++
> arch/arm/mach-omap2/prm-regbits-34xx.h | 3 +
> arch/arm/plat-omap/i2c.c | 124 ++++++---------
> arch/arm/plat-omap/include/plat/i2c.h | 16 ++
> arch/arm/plat-omap/include/plat/l4_3xxx.h | 24 +++
> drivers/i2c/busses/i2c-omap.c | 67 +++------
> include/linux/i2c-omap.h | 5 +
> 11 files changed, 881 insertions(+), 125 deletions(-)
> create mode 100644 arch/arm/plat-omap/include/plat/l4_3xxx.h
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-09-27 20:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 14:07 [PATCH v3 0/5] Convert I2C driver to use omap_device/runtime PM Rajendra Nayak
2010-09-21 14:07 ` [PATCH v3 1/5] OMAP2xxx: hwmod: add I2C hwmods for OMAP2420, 2430 Rajendra Nayak
2010-09-21 14:07 ` [PATCH v3 2/5] OMAP3: hwmod: add I2C hwmods for OMAP3430 Rajendra Nayak
2010-09-21 14:07 ` [PATCH v3 3/5] OMAP4: hwmod: add I2C hwmods for OMAP4430 Rajendra Nayak
2010-09-21 14:07 ` [PATCH v3 4/5] OMAP: I2C: split device registration and convert OMAP2+ to omap_device Rajendra Nayak
2010-09-21 14:07 ` [PATCH v3 5/5] OMAP: I2C: Convert i2c driver to use PM runtime api's Rajendra Nayak
2010-09-27 22:36 ` Ben Dooks
2010-09-28 5:58 ` Nayak, Rajendra
2010-09-28 6:59 ` Nayak, Rajendra
2010-09-28 7:48 ` Russell King - ARM Linux
2010-09-28 8:56 ` Nayak, Rajendra
2010-09-28 23:33 ` Ben Dooks
2010-09-29 4:00 ` Nayak, Rajendra
2010-10-07 17:37 ` Kevin Hilman
2010-10-27 7:35 ` Ben Dooks
2010-11-09 17:41 ` Kevin Hilman
2010-09-27 20:02 ` Kevin Hilman [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=87vd5rnee0.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.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).