linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shubhrajyoti <shubhrajyoti@ti.com>
To: Kevin Hilman <khilman@ti.com>
Cc: Ben Dooks <ben-i2c@fluff.org>,
	linux-i2c@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP4: I2C: Enable FIFO usage for OMAP4
Date: Thu, 03 Nov 2011 20:49:58 +0530	[thread overview]
Message-ID: <4EB2B11E.6010603@ti.com> (raw)
In-Reply-To: <87ipn1i8xd.fsf@ti.com>

On Thursday 03 November 2011 07:51 PM, Kevin Hilman wrote:
> Shubhrajyoti <shubhrajyoti@ti.com> writes:
>
>> On Thursday 14 July 2011 12:50 AM, Ben Dooks wrote:
>>> On Tue, Jul 05, 2011 at 05:01:01PM -0700, Kevin Hilman wrote:
>>>> Shubhrajyoti D <shubhrajyoti@ti.com> writes:
>>>>
>>>>> Currently the fifo depth is set to zero for OMAP4 which disables
>>>>> the FIFO usage. This patch enables the FIFO usage for I2C transactions
>>>>> on OMAP4 also.
>>>>>
>>>>> Tested on omap4430 and 3430.
>>>>>
>>>>> Reported-By: Nishanth Menon <nm@ti.com>
>>>>> Signed-off-by: Shubhrajyoti D <shubhrajyoti@ti.com>
>>>>> ---
>>>>> Rebased on top of the series by Andy Green
>>>>> http://www.spinics.net/lists/linux-i2c/msg05632.html
>>>> Thanks.
>>>>
>>>> This is v3.1 material, but would be nice to see a couple tested-by or
>>>> acked-by tags from folks that are more actively using the I2C driver
>>>> before merging
>>>>
>>>> Kevin
>>> guess you'll be picking these up?
>> Ben Could this patch be lined up as well?
> Please update this patch against my for_3.2/i2c-cleanup branch, and add
> the Tested-by from Nishanth Menon.
>
> Then I will push to get this in as a fix for v3.2-rc.
Thanks the patch was already rebased to the 

for_3.2/i2c-cleanup branch and applies on your tree . Resent it adding Nishanth's Tested-by

Thanks.

> Kevin


  reply	other threads:[~2011-11-03 15:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-05  7:11 [PATCH] OMAP4: I2C: Enable FIFO usage for OMAP4 Shubhrajyoti D
2011-07-06  0:01 ` Kevin Hilman
     [not found]   ` <8739ikp9aa.fsf-l0cyMroinI0@public.gmane.org>
2011-07-06  0:05     ` Menon, Nishanth
     [not found]       ` <CAOMWX4crxR0TQ38mFVkqv5eDQuEAry139+zoD2kKNm6imeR7yQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-07-06 14:30         ` Kevin Hilman
2011-07-13 19:20     ` Ben Dooks
     [not found]       ` <20110713192055.GC3369-RazCHl0VsYgkUSuvROHNpA@public.gmane.org>
2011-11-03 11:19         ` Shubhrajyoti
     [not found]           ` <4EB278C4.6030006-l0cyMroinI0@public.gmane.org>
2011-11-03 14:21             ` Kevin Hilman
2011-11-03 15:19               ` Shubhrajyoti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-03 15:17 Shubhrajyoti D
     [not found] ` <1320333428-23532-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
2011-11-08 20:01   ` Kevin Hilman
2011-06-29  6:00 Shubhrajyoti D
2011-06-29 23:23 ` Kevin Hilman
2011-06-30  7:24   ` Shubhrajyoti
2011-06-30 22:50     ` Kevin Hilman
     [not found]       ` <874o37djdg.fsf-l0cyMroinI0@public.gmane.org>
2011-07-05  7:11         ` 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=4EB2B11E.6010603@ti.com \
    --to=shubhrajyoti@ti.com \
    --cc=ben-i2c@fluff.org \
    --cc=khilman@ti.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-omap@vger.kernel.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).