From: ben-i2c@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 00/18] I2C: OMAP: I2C fixes, removal of cpu_is... from driver
Date: Tue, 7 Jun 2011 14:41:51 +0100 [thread overview]
Message-ID: <20110607134151.GE15795@trinity.fluff.org> (raw)
In-Reply-To: <1306973984-15165-1-git-send-email-khilman@ti.com>
On Wed, Jun 01, 2011 at 05:19:26PM -0700, Kevin Hilman wrote:
> Ben,
>
> Please pull in this series from Andy Green for the next merge window.
I'll have a look through this set as soon as possible.
> v4 is simply a rebase of Andy's v3 against v3.0-rc1 with some basic
> sanity testing against with the latest kernel.
>
> It's also available here for pulling:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.1/i2c-andy
>
> Original cover letter from Andy below:
>
> The following series removes cpu_...() usage completely from the
> omap-i2c driver by having decisions about functional implementation
> choices in the SoC held in cpu-specific hwmod tables that are
> already established, or for OMAP1 where there is no hwmod, set at
> OMAP1-specific i2c bus addition time.
>
> Along the way it solves two issues with the existing implementation,
> that only 16-bit accesses are documented to be allowed to the I2C
> peripheral unit, and that due to a confusion in the existing driver
> about whether it is faced with a newer IP version on OMAP3530, currently
> it writes to a random non-existent I2C register at times on that
> platform.
>
> The patch series is quite extended from the first try thanks to
> comments from Benoit Cousson.
>
> This 3rd try is based on 2.6.38-rc8 as requested.
>
> Andy Green (18):
> I2C: OMAP2+: Set hwmod flags to only allow 16-bit accesses to i2c
> I2C: OMAP2+: Name registers in I2C IP V2 only accordingly
> I2C: OMAP2+: Introduce I2C IP versioning constants
> I2C: OMAP2+: Tag all OMAP2+ hwmod defintions with I2C IP revision
> 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: OMAP2+: add correct functionality flags to all omap2plus i2c
> dev_attr
> 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/mach-omap2/omap_hwmod_2420_data.c | 8 ++-
> arch/arm/mach-omap2/omap_hwmod_2430_data.c | 6 ++
> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 13 ++++
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 18 ++++-
> 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 ++++++++
> 8 files changed, 153 insertions(+), 51 deletions(-)
>
> --
> 1.7.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Ben Dooks, ben at fluff.org, http://www.fluff.org/ben/
Large Hadron Colada: A large Pina Colada that makes the universe disappear.
next prev parent reply other threads:[~2011-06-07 13:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-02 0:19 [PATCH v4 00/18] I2C: OMAP: I2C fixes, removal of cpu_is... from driver Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 01/18] I2C: OMAP2+: Set hwmod flags to only allow 16-bit accesses to i2c Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 02/18] I2C: OMAP2+: Name registers in I2C IP V2 only accordingly Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 03/18] I2C: OMAP2+: Introduce I2C IP versioning constants Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 04/18] I2C: OMAP2+: Tag all OMAP2+ hwmod defintions with I2C IP revision Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 05/18] I2C: OMAP: add rev to omap i2c platform data Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 06/18] I2C: OMAP1: set IP revision in " Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 07/18] I2C: OMAP2+: Pass hwmod rev knowledge via platform_data when i2c bus added Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 08/18] I2C: OMAP2+: use platform_data ip revision to select register map Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 09/18] I2C: OMAP2+: Solve array bounds overflow error on i2c idle Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 10/18] I2C: OMAP2+: address confused probed version naming Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 11/18] I2C: OMAP2+: increase omap_i2c_dev_attr flags from u8 to u32 Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 12/18] I2C: OMAP1/OMAP2+: add flags field to omap i2c platform data Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 13/18] I2C: OMAP2+: Pass flags up to omap i2c platform_data as well Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 14/18] I2C: OMAP1/OMAP2+: create omap I2C functionality flags for each cpu_... test Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 15/18] I2C: OMAP2+: add correct functionality flags to all omap2plus i2c dev_attr Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 16/18] I2C: OMAP1: set i2c unit feature implementation flags in platform data Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 17/18] I2C: OMAP2+: Convert omap I2C driver to use feature implementation flags from " Kevin Hilman
2011-06-02 0:19 ` [PATCH v4 18/18] I2C: OMAP1/OMAP2+: prepend I2C IP version to probed version shown in dev_info Kevin Hilman
2011-06-07 13:41 ` Ben Dooks [this message]
2011-06-15 21:36 ` [PATCH v4 00/18] I2C: OMAP: I2C fixes, removal of cpu_is... from driver Ben Dooks
2011-06-15 23:27 ` Nicolas Pitre
2011-06-15 23:33 ` Kevin Hilman
2011-06-27 22:12 ` Kevin Hilman
2011-06-27 22:15 ` Kevin Hilman
2011-07-05 19:00 ` Kevin Hilman
2011-07-07 23:01 ` Ben Dooks
2011-07-08 15:14 ` 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=20110607134151.GE15795@trinity.fluff.org \
--to=ben-i2c@fluff.org \
--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).