linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J, KEERTHY" <j-keerthy-l0cyMroinI0@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Cc: ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Richard woodruff <r-woodruff2-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH v2] i2c-omap: Double clear of ARDY status in IRQ handler
Date: Fri, 18 Feb 2011 07:37:35 +0530	[thread overview]
Message-ID: <AANLkTin+g7RcMvuGY8FgFuxA+AWqyrhdZQQ+-PfGC1oQ@mail.gmail.com> (raw)
In-Reply-To: <20110218000843.GP20795-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>

On Fri, Feb 18, 2011 at 5:38 AM, Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org> wrote:
> * Keerthy <j-keerthy-l0cyMroinI0@public.gmane.org> [110215 20:53]:
>> From: Richard woodruff <r-woodruff2-l0cyMroinI0@public.gmane.org>
>>
>> This errata occurs when the ARDY interrupt generation is enabled.
>> At the begining of every new transaction the ARDY interrupt is cleared.
>>
>> On continuous i2c transactions where after clearing the ARDY bit from
>> I2C_STAT register (clearing the interrupt), the IRQ line is reasserted and the
>> I2C_STAT[ARDY] bit set again on 1. In fact, the ARDY status bit is not cleared
>> at the write access to I2C_STAT[ARDY] and only the IRQ line is deasserted and
>> then reasserted. This is not captured in the usual errata documents.
>>
>> The workaround is to have a double clear of ARDY status in irq handler.
>
> I'll add this to omap-testing for few days and then if no issue Ben
> can merge this.

Thanks Tony.
>
> Regards,
>
> Tony
>
>> Signed-off-by: Richard woodruff <r-woodruff2-l0cyMroinI0@public.gmane.org>
>> Signed-off-by: Keerthy <j-keerthy-l0cyMroinI0@public.gmane.org>
>> ---
>>  drivers/i2c/busses/i2c-omap.c |    6 +++++-
>>  1 files changed, 5 insertions(+), 1 deletions(-)
>>
>> diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
>> index b605ff3..5b35cf4 100644
>> --- a/drivers/i2c/busses/i2c-omap.c
>> +++ b/drivers/i2c/busses/i2c-omap.c
>> @@ -847,11 +847,15 @@ complete:
>>                       dev_err(dev->dev, "Arbitration lost\n");
>>                       err |= OMAP_I2C_STAT_AL;
>>               }
>> +             /*
>> +              * ProDB0017052: Clear ARDY bit twice
>> +              */
>>               if (stat & (OMAP_I2C_STAT_ARDY | OMAP_I2C_STAT_NACK |
>>                                       OMAP_I2C_STAT_AL)) {
>>                       omap_i2c_ack_stat(dev, stat &
>>                               (OMAP_I2C_STAT_RRDY | OMAP_I2C_STAT_RDR |
>> -                             OMAP_I2C_STAT_XRDY | OMAP_I2C_STAT_XDR));
>> +                             OMAP_I2C_STAT_XRDY | OMAP_I2C_STAT_XDR |
>> +                             OMAP_I2C_STAT_ARDY));
>>                       omap_i2c_complete_cmd(dev, err);
>>                       return IRQ_HANDLED;
>>               }
>> --
>> 1.7.0.4
>>
>> --
>> 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
>



-- 
Regards and Thanks,
Keerthy

      parent reply	other threads:[~2011-02-18  2:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16  4:54 [PATCH v2] i2c-omap: Double clear of ARDY status in IRQ handler Keerthy
2011-02-18  0:08 ` Tony Lindgren
     [not found]   ` <20110218000843.GP20795-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2011-02-18  2:07     ` J, KEERTHY [this message]

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=AANLkTin+g7RcMvuGY8FgFuxA+AWqyrhdZQQ+-PfGC1oQ@mail.gmail.com \
    --to=j-keerthy-l0cymroini0@public.gmane.org \
    --cc=ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=r-woodruff2-l0cyMroinI0@public.gmane.org \
    --cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@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).