From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Robert Foss <robert.foss@linaro.org>
Cc: loic.poulain@linaro.org, linux-i2c@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] i2c: qcom: Fix IRQ error misassignement
Date: Thu, 26 Nov 2020 20:33:34 +0530 [thread overview]
Message-ID: <20201126150334.GC51288@thinkpad> (raw)
In-Reply-To: <20201126145321.18269-1-robert.foss@linaro.org>
On Thu, Nov 26, 2020 at 03:53:21PM +0100, Robert Foss wrote:
> During cci_isr() errors read from register fields belonging to
> i2c master1 are currently assigned to the status field belonging to
s/correctly/incorrectly
> i2c master0. This patch corrects this error, and always assigns
> master1 errors to the status field of master1.
>
This patch fixes a legitimate bug. So there should be a fixes tag!
> Suggested-by: Loic Poulain <loic.poulain@linaro.org>
Reported-by?
Thanks,
Mani
> Signed-off-by: Robert Foss <robert.foss@linaro.org>
> ---
> drivers/i2c/busses/i2c-qcom-cci.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-qcom-cci.c b/drivers/i2c/busses/i2c-qcom-cci.c
> index f13735beca58..1c259b5188de 100644
> --- a/drivers/i2c/busses/i2c-qcom-cci.c
> +++ b/drivers/i2c/busses/i2c-qcom-cci.c
> @@ -194,9 +194,9 @@ static irqreturn_t cci_isr(int irq, void *dev)
> if (unlikely(val & CCI_IRQ_STATUS_0_I2C_M1_ERROR)) {
> if (val & CCI_IRQ_STATUS_0_I2C_M1_Q0_NACK_ERR ||
> val & CCI_IRQ_STATUS_0_I2C_M1_Q1_NACK_ERR)
> - cci->master[0].status = -ENXIO;
> + cci->master[1].status = -ENXIO;
> else
> - cci->master[0].status = -EIO;
> + cci->master[1].status = -EIO;
>
> writel(CCI_HALT_REQ_I2C_M1_Q0Q1, cci->base + CCI_HALT_REQ);
> ret = IRQ_HANDLED;
> --
> 2.27.0
>
next prev parent reply other threads:[~2020-11-26 15:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 14:53 [PATCH v1] i2c: qcom: Fix IRQ error misassignement Robert Foss
2020-11-26 15:03 ` Manivannan Sadhasivam [this message]
2020-11-26 15:58 ` Robert Foss
2020-11-26 16:10 ` Manivannan Sadhasivam
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=20201126150334.GC51288@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=robert.foss@linaro.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).