From: Kevin Hilman <khilman@ti.com>
To: Rajendra Nayak <rnayak@ti.com>, ben-linux@fluff.org
Cc: paul@pwsan.com, linux-omap@vger.kernel.org,
santosh.shilimkar@ti.com, linux-i2c@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] i2c-omap: Program I2C_WE on OMAP4 to enable i2c wakeup
Date: Fri, 04 Mar 2011 09:00:00 -0800 [thread overview]
Message-ID: <87ei6mizxr.fsf@ti.com> (raw)
In-Reply-To: <1299245544-23790-1-git-send-email-rnayak@ti.com> (Rajendra Nayak's message of "Fri, 4 Mar 2011 19:02:24 +0530")
Rajendra Nayak <rnayak@ti.com> writes:
> For the I2C module to be wakeup capable, programming I2C_WE
> register (which was skipped for OMAP4430) is needed
> even on OMAP4.
> This fixes i2c controller timeouts which were seen recently
> with the static dependency being cleared between MPU and
> L4PER clockdomains.
>
> Signed-off-by: Rajendra Nayak <rnayak@ti.com>
> ---
> Patch is based on 2.6.38-rc7 kernel.
Acked-by: Kevin Hilman <khilman@ti.com>
Ben, looks like another fix that should be queued for 2.6.38-rc.
Thanks,
Kevin
>
> drivers/i2c/busses/i2c-omap.c | 4 +---
> 1 files changed, 1 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
> index 829a2a1..58a58c7 100644
> --- a/drivers/i2c/busses/i2c-omap.c
> +++ b/drivers/i2c/busses/i2c-omap.c
> @@ -378,9 +378,7 @@ static int omap_i2c_init(struct omap_i2c_dev *dev)
> * REVISIT: Some wkup sources might not be needed.
> */
> dev->westate = OMAP_I2C_WE_ALL;
> - if (dev->rev < OMAP_I2C_REV_ON_4430)
> - omap_i2c_write_reg(dev, OMAP_I2C_WE_REG,
> - dev->westate);
> + omap_i2c_write_reg(dev, OMAP_I2C_WE_REG, dev->westate);
> }
> }
> omap_i2c_write_reg(dev, OMAP_I2C_CON_REG, 0);
next prev parent reply other threads:[~2011-03-04 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 13:32 [PATCH] i2c-omap: Program I2C_WE on OMAP4 to enable i2c wakeup Rajendra Nayak
2011-03-04 17:00 ` Kevin Hilman [this message]
[not found] ` <87ei6mizxr.fsf-l0cyMroinI0@public.gmane.org>
2011-03-04 17:17 ` Ben Dooks
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=87ei6mizxr.fsf@ti.com \
--to=khilman@ti.com \
--cc=ben-linux@fluff.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@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).