From: Shubhrajyoti <shubhrajyoti-l0cyMroinI0@public.gmane.org>
To: Shubhrajyoti D <shubhrajyoti-l0cyMroinI0@public.gmane.org>
Cc: linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org,
Kevin Hilman <khilman-l0cyMroinI0@public.gmane.org>,
Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Subject: Re: [PATCH 00/10] I2C updates
Date: Fri, 24 Feb 2012 15:00:52 +0530 [thread overview]
Message-ID: <4F4758CC.4010607@ti.com> (raw)
In-Reply-To: <1328882405-15284-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
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 <khilman-l0cyMroinI0@public.gmane.org>
> Cc: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.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(-)
>
next prev parent reply other threads:[~2012-02-24 9:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 13:59 [PATCH 00/10] I2C updates Shubhrajyoti D
2012-02-10 13:59 ` [PATCH 01/10] I2C : OMAP : make omap_i2c_unidle/idle functions depend on CONFIG_PM_RUNTIME Shubhrajyoti D
2012-02-10 13:59 ` [PATCH 02/10] OMAP : I2C : Remove reset at init Shubhrajyoti D
[not found] ` <1328882405-15284-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
2012-02-10 13:59 ` [PATCH 03/10] I2C: OMAP: Recover from Bus Busy condition Shubhrajyoti D
2012-02-10 13:59 ` [PATCH 04/10] OMAP: I2C: I2C register restore only if context is lost Shubhrajyoti D
2012-02-10 14:00 ` [PATCH 05/10] OMAP: I2C: Fix the interrupt clearing in OMAP4 Shubhrajyoti D
2012-02-10 14:00 ` [PATCH 08/10] OMAP: I2C: Fix the error handling Shubhrajyoti D
2012-02-24 9:30 ` Shubhrajyoti [this message]
2012-02-10 14:00 ` [PATCH 06/10] OMAP: I2C: Fix the mismatch of pm_runtime enable and disable Shubhrajyoti D
2012-02-10 14:00 ` [PATCH 07/10] OMAP: I2C: add devexit to the remove code Shubhrajyoti D
2012-02-10 14:00 ` [PATCH 09/10] I2C: OMAP: Correct I2C revision for OMAP3 Shubhrajyoti D
2012-02-10 14:00 ` [PATCH 10/10] I2C: OMAP: Don't check if wait_for_completion_timeout() returns less than zero Shubhrajyoti D
2012-02-14 6:12 ` [PATCH 00/10] I2C updates Hebbar, Gururaja
2012-02-14 9:11 ` Shubhrajyoti
2012-02-24 9:31 ` Shubhrajyoti
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=4F4758CC.4010607@ti.com \
--to=shubhrajyoti-l0cymroini0@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=khilman-l0cyMroinI0@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).