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: Tue, 05 Jul 2011 17:01:01 -0700 [thread overview]
Message-ID: <8739ikp9aa.fsf@ti.com> (raw)
In-Reply-To: <1309849870-25660-1-git-send-email-shubhrajyoti@ti.com> (Shubhrajyoti D.'s message of "Tue, 5 Jul 2011 12:41:10 +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.
>
> 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
> 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) /
next prev parent reply other threads:[~2011-07-06 0:01 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 [this message]
[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
-- 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=8739ikp9aa.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).