From: Wolfram Sang <wsa@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: aisheng.dong@nxp.com, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, carlos.song@nxp.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 v4] i2c: imx-lpi2c: directly return ISR when detect a NACK
Date: Mon, 14 Aug 2023 17:02:09 +0200 [thread overview]
Message-ID: <ZNpB8fWnOcH8997V@shikoro> (raw)
In-Reply-To: <169100562766.1919254.12222013232053766298.b4-ty@kernel.org>
[-- Attachment #1.1: Type: text/plain, Size: 600 bytes --]
On Wed, Aug 02, 2023 at 10:10:31PM +0200, Andi Shyti wrote:
> Hi
>
> On Thu, 27 Jul 2023 11:03:47 +0800, carlos.song@nxp.com wrote:
> > A NACK flag in ISR means i2c bus error. In such condition,
> > there is no need to do read/write operation.
> >
> > In this patch, i2c will check MSR_NDF, MSR_RDF and MSR_TDF
> > flag in turn, it's making mutually exclusive NACK/read/write.
> > So when a NACK is received(MSR_NDF), i2c will return ISR
> > directly and then stop i2c transfer.
> >
> > [...]
>
> Applied to i2c/andi-for-next on
Applied to for-next (via Andi's tree), thanks!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-08-14 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 3:03 [PATCH v4] i2c: imx-lpi2c: directly return ISR when detect a NACK carlos.song
2023-07-27 8:38 ` Andi Shyti
2023-08-02 20:10 ` Andi Shyti
2023-08-14 15:02 ` Wolfram Sang [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=ZNpB8fWnOcH8997V@shikoro \
--to=wsa@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=andi.shyti@kernel.org \
--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