From: khilman@ti•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] OMAP I2C cleanups for v3.1
Date: Fri, 08 Jul 2011 09:22:03 -0700 [thread overview]
Message-ID: <87liw8agk4.fsf@ti.com> (raw)
Tony,
Please pull the I2C cleanup changes below for v3.1.
This is the same series from Andy Green that has been
posted/reviewed/tested many times except the omap_hwmod data patches
have been separated out into a separate series.
This version also has an Ack from Ben Dooks for merge via linux-omap.
Kevin
The following changes since commit fe0d42203cb5616eeff68b14576a0f7e2dd56625:
Linux 3.0-rc6 (2011-07-04 15:56:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.1/i2c-andy
Andy Green (15):
I2C: OMAP2+: Name registers in I2C IP V2 only accordingly
I2C: OMAP2+: Introduce I2C IP versioning constants
I2C: OMAP: add rev to omap i2c platform data
I2C: OMAP1: set IP revision in platform data
I2C: OMAP2+: Pass hwmod rev knowledge via platform_data when i2c bus added
I2C: OMAP2+: use platform_data ip revision to select register map
I2C: OMAP2+: Solve array bounds overflow error on i2c idle
I2C: OMAP2+: address confused probed version naming
I2C: OMAP2+: increase omap_i2c_dev_attr flags from u8 to u32
I2C: OMAP1/OMAP2+: add flags field to omap i2c platform data
I2C: OMAP2+: Pass flags up to omap i2c platform_data as well
I2C: OMAP1/OMAP2+: create omap I2C functionality flags for each cpu_... test
I2C: OMAP1: set i2c unit feature implementation flags in platform data
I2C: OMAP2+: Convert omap I2C driver to use feature implementation flags from platform data
I2C: OMAP1/OMAP2+: prepend I2C IP version to probed version shown in dev_info
arch/arm/plat-omap/i2c.c | 27 +++++++++
arch/arm/plat-omap/include/plat/i2c.h | 3 +-
drivers/i2c/busses/i2c-omap.c | 100 ++++++++++++++++++---------------
include/linux/i2c-omap.h | 29 ++++++++++
4 files changed, 113 insertions(+), 46 deletions(-)
next reply other threads:[~2011-07-08 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 16:22 Kevin Hilman [this message]
[not found] ` <AA48DD8077D5D945A49BD1782C1140F1011EBBC7@fioues08.ebgroup.elektrobit.com>
2012-01-27 19:02 ` [GIT PULL] OMAP PM EMU fix for v3.3 Tony Lindgren
2012-01-28 7:58 ` Madhusudhan.Gowda at elektrobit.com
2012-02-20 9:52 ` Madhusudhan.Gowda at elektrobit.com
2012-02-20 15:29 ` Kevin Hilman
2012-02-22 8:42 ` Madhusudhan.Gowda at elektrobit.com
2012-02-23 4:09 ` Paul Walmsley
2012-02-23 9:49 ` Madhusudhan.Gowda at elektrobit.com
2012-02-24 0:11 ` Paul Walmsley
2012-02-24 9:20 ` Madhusudhan.Gowda at elektrobit.com
2012-02-24 21:03 ` 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=87liw8agk4.fsf@ti.com \
--to=khilman@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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