From: Nishanth Menon <nm@ti.com>
To: "Sonasath, Moiz" <m-sonasath@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Kamat, Nishant" <nskamat@ti.com>, Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 2/3] [OMAP:I2C]In case of a NACK|ARDY|AL return from the ISR
Date: Wed, 15 Jul 2009 16:37:04 -0500 [thread overview]
Message-ID: <4A5E4C00.6090407@ti.com> (raw)
In-Reply-To: <CD8CC2B65FEE304DA95744A5472698F202957C7C2D@dlee06.ent.ti.com>
Sonasath, Moiz had written, on 07/15/2009 10:25 AM, the following:
>> diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
>> index d280acf..05b5e4c 100644
>> --- a/drivers/i2c/busses/i2c-omap.c
>> +++ b/drivers/i2c/busses/i2c-omap.c
>> @@ -685,8 +685,10 @@ omap_i2c_isr(int this_irq, void *dev_id)
>> err |= OMAP_I2C_STAT_AL;
>> }
>> if (stat & (OMAP_I2C_STAT_ARDY | OMAP_I2C_STAT_NACK |
>> - OMAP_I2C_STAT_AL))
>> + OMAP_I2C_STAT_AL)) {
>> omap_i2c_complete_cmd(dev, err);
>> + return IRQ_HANDLED;
>> + }
> What is the status of IRQ_STAT register? Who will clear that if we return immediately from ISR? Isr will be reinvoked and we'd handle the same anyways..
>
> [Moiz]
> Correct me if I am wrong, but you are referring to the OMAP_I2C_STAT_REG (which has the interrupt status information).
>This is actually ACKED just before going into the NACK|AL|ARDY error
cases. I suppose a few days back you also sent out a
>atch to change this to ACK all interrupts other than RRDY/RDR and
XRDY/XDR as we have to ACK these only after we service them.
>
> I think this conflicts with [1]
> [Moiz]
> Actually, it does not conflict with [1], as [1] changes the later part of the code allowing this patch to be applied cleanly.
Got it. Thanks for clarifying. my bad.
Acked-by: Nishanth Menon <nm@ti.com>
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2009-07-15 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 21:19 [PATCH 2/3] [OMAP:I2C]In case of a NACK|ARDY|AL return from the ISR Sonasath, Moiz
2009-07-14 22:21 ` Menon, Nishanth
2009-07-15 15:25 ` Sonasath, Moiz
2009-07-15 21:37 ` Nishanth Menon [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-21 15:14 Sonasath, Moiz
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=4A5E4C00.6090407@ti.com \
--to=nm@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=m-sonasath@ti.com \
--cc=nskamat@ti.com \
--cc=paul@pwsan.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 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.