linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Shubhrajyoti D <shubhrajyoti@ti.com>
Cc: linux-i2c@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP4: I2C: Enable FIFO usage for OMAP4
Date: Wed, 29 Jun 2011 16:23:57 -0700	[thread overview]
Message-ID: <871uycql0y.fsf@ti.com> (raw)
In-Reply-To: <1309327221-4121-1-git-send-email-shubhrajyoti@ti.com> (Shubhrajyoti D.'s message of "Wed, 29 Jun 2011 11:30:21 +0530")

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.

Do you know the history of why the FIFO depth was set to zero?  A
summary of that history would greatly help reviewers.

> Reported-By:Nishanth Menon <nm@ti.com>

minor: missing space after ':'

> Signed-off-by: Shubhrajyoti D <shubhrajyoti@ti.com>

Tested on what platforms?   OMAP3 also?

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? 

Thanks,

Kevin

[1] git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git


  reply	other threads:[~2011-06-29 23:23 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 [this message]
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
  -- 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=871uycql0y.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=shubhrajyoti@ti.com \
    /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).