From: Kevin Hilman <khilman-l0cyMroinI0@public.gmane.org>
To: "Menon, Nishanth" <nm-l0cyMroinI0@public.gmane.org>
Cc: Shubhrajyoti D <shubhrajyoti-l0cyMroinI0@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] OMAP4: I2C: Enable FIFO usage for OMAP4
Date: Wed, 06 Jul 2011 07:30:48 -0700 [thread overview]
Message-ID: <87ei23jxbb.fsf@ti.com> (raw)
In-Reply-To: <CAOMWX4crxR0TQ38mFVkqv5eDQuEAry139+zoD2kKNm6imeR7yQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (Nishanth Menon's message of "Tue, 5 Jul 2011 17:05:48 -0700")
"Menon, Nishanth" <nm-l0cyMroinI0@public.gmane.org> writes:
> On Tue, Jul 5, 2011 at 17:01, Kevin Hilman <khilman-l0cyMroinI0@public.gmane.org> wrote:
>>
>> Shubhrajyoti D <shubhrajyoti-l0cyMroinI0@public.gmane.org> 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-l0cyMroinI0@public.gmane.org>
>> > Signed-off-by: Shubhrajyoti D <shubhrajyoti-l0cyMroinI0@public.gmane.org>
>> > ---
>> > 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
>
> For what it is worth: tested on SDP4460/4430 with 255 multi-byte i2c
> read operation on twl6030.
>
> Tested-by: Nishanth Menon <nm-l0cyMroinI0@public.gmane.org>
>
Thanks Nishanth,
Kevin
next prev parent reply other threads:[~2011-07-06 14:30 UTC|newest]
Thread overview: 17+ 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2011-11-03 15:17 Shubhrajyoti D
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-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=87ei23jxbb.fsf@ti.com \
--to=khilman-l0cymroini0@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nm-l0cyMroinI0@public.gmane.org \
--cc=shubhrajyoti-l0cyMroinI0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.