Shubhrajyoti D <shubhrajyoti@xxxxxx> 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@xxxxxx>
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@xxxxxx>
> ---
> 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 */
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
