From: Kevin Hilman <khilman-l0cyMroinI0@public.gmane.org>
To: Shubhrajyoti D <shubhrajyoti-l0cyMroinI0@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org,
Vikram Pandita <vikram.pandita-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH v4] OMAP: I2C: Fix the interrupt clearing in OMAP4
Date: Fri, 02 Dec 2011 14:42:58 -0800 [thread overview]
Message-ID: <8739d2mw7h.fsf@ti.com> (raw)
In-Reply-To: <1322491212-8657-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org> (Shubhrajyoti D.'s message of "Mon, 28 Nov 2011 20:10:12 +0530")
Shubhrajyoti D <shubhrajyoti-l0cyMroinI0@public.gmane.org> writes:
> On OMAP4 we were writing 1 to IRQENABLE_CLR which cleared only
> the arbitration lost interrupt however for other ips (not OMAP_I2C_IP_VERSION_2)
> we clear all the interrupts at idle. The patch intends to fix the same by writing 0 to the
> IE register.
Please also explain why you're using a different register to clear interrupts.
IMO, you don't need to explain how it works on other IPs.
The changelog should just explain what's broken in the handling of the
v2 interrupts (only arbitration lost interrupt is cleared) and how
you're fixing it (writing zero to IE REG, which clears all interrupts.)
> Signed-off-by: Vikram Pandita <vikram.pandita-l0cyMroinI0@public.gmane.org>
Has Vikram really signed off on this? This is a different
implementation from his original version. Unless he is on the delivery
path, there should not be a signed-off from him. Instead, as I've
suggested already, I'd like to see a comment in the changelog mentioning
that this patch is based on an original patch from Vikram, and then
ideally a reply from Vikram on the list with his Acked-by or Reviewed-by.
Kevin
> Signed-off-by: Shubhrajyoti D <shubhrajyoti-l0cyMroinI0@public.gmane.org>
> ---
> drivers/i2c/busses/i2c-omap.c | 6 ++----
> 1 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
> index a43d002..abadc13 100644
> --- a/drivers/i2c/busses/i2c-omap.c
> +++ b/drivers/i2c/busses/i2c-omap.c
> @@ -297,10 +297,8 @@ static void omap_i2c_idle(struct omap_i2c_dev *dev)
> pdata = dev->dev->platform_data;
>
> dev->iestate = omap_i2c_read_reg(dev, OMAP_I2C_IE_REG);
> - if (pdata->rev == OMAP_I2C_IP_VERSION_2)
> - omap_i2c_write_reg(dev, OMAP_I2C_IP_V2_IRQENABLE_CLR, 1);
> - else
> - omap_i2c_write_reg(dev, OMAP_I2C_IE_REG, 0);
> +
> + omap_i2c_write_reg(dev, OMAP_I2C_IE_REG, 0);
>
> if (dev->rev < OMAP_I2C_OMAP1_REV_2) {
> iv = omap_i2c_read_reg(dev, OMAP_I2C_IV_REG); /* Read clears */
prev parent reply other threads:[~2011-12-02 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 14:40 [PATCH v4] OMAP: I2C: Fix the interrupt clearing in OMAP4 Shubhrajyoti D
[not found] ` <1322491212-8657-1-git-send-email-shubhrajyoti-l0cyMroinI0@public.gmane.org>
2011-12-02 22:42 ` Kevin Hilman [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=8739d2mw7h.fsf@ti.com \
--to=khilman-l0cymroini0@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shubhrajyoti-l0cyMroinI0@public.gmane.org \
--cc=vikram.pandita-l0cyMroinI0@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).