From: Shubhrajyoti <shubhrajyoti-l0cyMroinI0@public.gmane.org>
To: Kevin Hilman <khilman-l0cyMroinI0@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] OMAP4: I2C: Enable FIFO usage for OMAP4
Date: Tue, 05 Jul 2011 12:41:24 +0530 [thread overview]
Message-ID: <4E12B91C.8020102@ti.com> (raw)
In-Reply-To: <874o37djdg.fsf-l0cyMroinI0@public.gmane.org>
On Friday 01 July 2011 04:20 AM, Kevin Hilman wrote:
> Shubhrajyoti<shubhrajyoti-l0cyMroinI0@public.gmane.org> writes:
>
>> On Thursday 30 June 2011 04:53 AM, Kevin Hilman 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.
>>> Do you know the history of why the FIFO depth was set to zero? A
>>> summary of that history would greatly help reviewers.
Looks like it is disabled in the initial bring up and some how didn’t
get enabled.
All I could find is
http://www.mail-archive.com/linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org/msg01404.html
>>>> Reported-By:Nishanth Menon<nm-l0cyMroinI0@public.gmane.org>
>>> minor: missing space after ':'
Yes will fix it.
>>>> Signed-off-by: Shubhrajyoti D<shubhrajyoti-l0cyMroinI0@public.gmane.org>
>>> Tested on what platforms? OMAP3 also?
>> OMAP4 and OMAP3
> Please add a brief summary of what platforms it was tested on in the
> changelog.
Will update it
>>> Could you please rebase this onto my for_3.1/i2c-andy branch[1] where we
>>> have a large series of I2C patches queued up for the v3.1 merge window
>>> already?
>> OK will rebase and resend.
Sent a rebased version.
> Thanks,
>
> Kevin
next prev parent reply other threads:[~2011-07-05 7:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 6:00 [PATCH] OMAP4: I2C: Enable FIFO usage for OMAP4 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-07-05 7:11 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
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
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=4E12B91C.8020102@ti.com \
--to=shubhrajyoti-l0cymroini0@public.gmane.org \
--cc=khilman-l0cyMroinI0@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).