From: Andi Shyti <andi.shyti@kernel.org>
To: carlos.song@nxp.com
Cc: aisheng.dong@nxp.com, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, xiaoning.wang@nxp.com, haibo.chen@nxp.com,
linux-imx@nxp.com, linux-i2c@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] i2c: imx-lpi2c: directly return ISR when detect a NACK
Date: Wed, 26 Jul 2023 01:55:11 +0200 [thread overview]
Message-ID: <20230725235511.lt62ubfw7geu5cfu@intel.intel> (raw)
In-Reply-To: <20230724105546.1964059-1-carlos.song@nxp.com>
Hi Carlos,
On Mon, Jul 24, 2023 at 06:55:44PM +0800, carlos.song@nxp.com wrote:
> From: Gao Pan <pandy.gao@nxp.com>
>
> A NACK flag in ISR means i2c bus error. In such codition,
> there is no need to do read/write operation. It's better
> to return ISR directly and then stop i2c transfer.
>
> Fixes: a55fa9d0e42e ("i2c: imx-lpi2c: add low power i2c bus driver")
> Signed-off-by: Gao Pan <pandy.gao@nxp.com>
> Signed-off-by: Carlos Song <carlos.song@nxp.com>
> ---
> drivers/i2c/busses/i2c-imx-lpi2c.c | 11 +++++------
> 1 file changed, 5 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-imx-lpi2c.c b/drivers/i2c/busses/i2c-imx-lpi2c.c
> index c3287c887c6f..158de0b7f030 100644
> --- a/drivers/i2c/busses/i2c-imx-lpi2c.c
> +++ b/drivers/i2c/busses/i2c-imx-lpi2c.c
> @@ -514,15 +514,14 @@ static irqreturn_t lpi2c_imx_isr(int irq, void *dev_id)
> temp = readl(lpi2c_imx->base + LPI2C_MSR);
> temp &= enabled;
>
> - if (temp & MSR_RDF)
> + if (temp & MSR_NDF) {
> + complete(&lpi2c_imx->complete);
> + return IRQ_HANDLED;
you can actually remove the return here
if (temp & MSR_NDF)
complete();
else if (temp & MSR_RDF)
exfifo();
else if (temp & MSR_TDF)
txfifo();
return IRQ_HANDLED;
BTW, the logic here is changing, as well and it's not described
in the commit log. This patch is not only stopping when a nack is
received (MSR_NDF), but it's also making mutually exclusive
read/write (which I guess are MSR_RDF and MSR_TDF).
Is this what you want? If so, can you please describe it in the
commit log or add a comment describing that the three states are
all mutually exclusive.
Thanks,
Andi
> + } else if (temp & MSR_RDF)
> lpi2c_imx_read_rxfifo(lpi2c_imx);
> -
> - if (temp & MSR_TDF)
> + else if (temp & MSR_TDF)
> lpi2c_imx_write_txfifo(lpi2c_imx);
>
> - if (temp & MSR_NDF)
> - complete(&lpi2c_imx->complete);
> -
> return IRQ_HANDLED;
> }
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-07-25 23:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 10:55 [PATCH v2 1/3] i2c: imx-lpi2c: directly return ISR when detect a NACK carlos.song
2023-07-24 10:55 ` [PATCH v2 2/3] i2c: imx-lpi2c: add bus recovery feature carlos.song
2023-07-26 14:11 ` Andi Shyti
2023-07-28 9:48 ` Carlos Song
2023-07-24 10:55 ` [PATCH v2 3/3] i2c: imx-lpi2c: add debug message when i2c peripheral clk doesn't work carlos.song
2023-07-24 12:38 ` Fabio Estevam
2023-07-25 1:59 ` [EXT] " Carlos Song
2023-07-25 23:55 ` Andi Shyti [this message]
2023-07-26 7:58 ` [EXT] Re: [PATCH v2 1/3] i2c: imx-lpi2c: directly return ISR when detect a NACK Carlos Song
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=20230725235511.lt62ubfw7geu5cfu@intel.intel \
--to=andi.shyti@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=carlos.song@nxp.com \
--cc=festevam@gmail.com \
--cc=haibo.chen@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=xiaoning.wang@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox