All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shubhrajyoti <shubhrajyoti-l0cyMroinI0@public.gmane.org>
To: Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Cc: Kevin Hilman <khilman-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: Thu, 03 Nov 2011 16:49:32 +0530	[thread overview]
Message-ID: <4EB278C4.6030006@ti.com> (raw)
In-Reply-To: <20110713192055.GC3369-RazCHl0VsYgkUSuvROHNpA@public.gmane.org>

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-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
>>
>> Kevin
> guess you'll be picking these up?

Ben Could this patch be lined up as well?
>  
>>>  drivers/i2c/busses/i2c-omap.c |   11 ++++++-----
>>>  1 files changed, 6 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
>>> index d53cd61..8f87a37 100644
>>> --- a/drivers/i2c/busses/i2c-omap.c
>>> +++ b/drivers/i2c/busses/i2c-omap.c
>>> @@ -1068,13 +1068,14 @@ omap_i2c_probe(struct platform_device *pdev)
>>>  		 * size. This is to ensure that we can handle the status on int
>>>  		 * call back latencies.
>>>  		 */
>>> -		if (dev->rev >= OMAP_I2C_REV_ON_3530_4430) {
>>> -			dev->fifo_size = 0;
>>> +
>>> +		dev->fifo_size = (dev->fifo_size / 2);
>>> +
>>> +		if (dev->rev >= OMAP_I2C_REV_ON_3530_4430)
>>>  			dev->b_hw = 0; /* Disable hardware fixes */
>>> -		} else {
>>> -			dev->fifo_size = (dev->fifo_size / 2);
>>> +		else
>>>  			dev->b_hw = 1; /* Enable hardware fixes */
>>> -		}
>>> +
>>>  		/* calculate wakeup latency constraint for MPU */
>>>  		if (dev->set_mpu_wkup_lat != NULL)
>>>  			dev->latency = (1000000 * dev->fifo_size) /
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
>> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2011-11-03 11:19 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
2011-07-13 19:20     ` Ben Dooks
     [not found]       ` <20110713192055.GC3369-RazCHl0VsYgkUSuvROHNpA@public.gmane.org>
2011-11-03 11:19         ` Shubhrajyoti [this message]
     [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=4EB278C4.6030006@ti.com \
    --to=shubhrajyoti-l0cymroini0@public.gmane.org \
    --cc=ben-i2c-elnMNo+KYs3YtjvyW6yDsg@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 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.