Thread (15 messages) 15 messages, 2 authors, 2012-02-24
DORMANTno replies
Revisions (6)
  1. v1 [diff vs current]
  2. v1 [diff vs current]
  3. v1 [diff vs current]
  4. v1 current
  5. v1 [diff vs current]
  6. v1 [diff vs current]

[PATCH 00/10] I2C updates

From: Shubhrajyoti <hidden>
Date: 2012-02-24 09:31:45
Also in: linux-i2c, linux-omap

On Friday 10 February 2012 07:29 PM, Shubhrajyoti D wrote:
This patch series colates the various i2c updates into
a series.  Since it is collection of various patches
the version info is not retained, however most of them undergone
multiple versions.
If there are no further comments can this be queued.
This is rebased to linus head commit 63082402968f4b73f10b28a8ac1f3da821aeb82d

The patch series does the following 

- Warn fixes if CONFIG_PM_RUNTIME is not selected.
- I2C register restore only if context if the context is lost
- Bus busy recovery mechanism.
- the reset is not done in init.

Tested on omap4sdp and omap3sdp. 


Cc: Kevin Hilman <redacted>
Cc: Ben Dooks <ben-linux@fluff.org>

Jon Hunter (1):
  I2C: OMAP: Correct I2C revision for OMAP3

Shubhrajyoti D (8):
  I2C : OMAP : make omap_i2c_unidle/idle functions depend on
    CONFIG_PM_RUNTIME
  OMAP : I2C : Remove reset at init
  OMAP: I2C: I2C register restore only if context is lost
  OMAP: I2C: Fix the interrupt clearing in OMAP4
  OMAP: I2C: Fix the mismatch of pm_runtime enable and disable
  OMAP: I2C: Optimise the remove code
  OMAP: I2C: Fix the error handling
  I2C: OMAP: Don't check if wait_for_completion_timeout() returns less
    than zero

Vikram Pandita (1):
  I2C: OMAP: Recover from Bus Busy condition

 drivers/i2c/busses/i2c-omap.c |  173 ++++++++++++++++++++++++-----------------
 1 files changed, 101 insertions(+), 72 deletions(-)
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help