From: Wolfram Sang <wsa@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/4] i2c: mpc: Interrupt driven transfer
Date: Tue, 13 Apr 2021 14:22:58 +0200 [thread overview]
Message-ID: <20210413122258.GC1553@kunai> (raw)
In-Reply-To: <20210413050956.23264-3-chris.packham@alliedtelesis.co.nz>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
On Tue, Apr 13, 2021 at 05:09:53PM +1200, Chris Packham wrote:
> The fsl-i2c controller will generate an interrupt after every byte
> transferred. Make use of this interrupt to drive a state machine which
> allows the next part of a transfer to happen as soon as the interrupt is
> received. This is particularly helpful with SMBUS devices like the LM81
> which will timeout if we take too long between bytes in a transfer.
>
> Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
Thanks for the update. I'll wait a little, because IIRC Andy wanted to
review.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-13 12:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 5:09 [PATCH v3 0/4] i2c: mpc: Refactor to improve responsiveness Chris Packham
2021-04-13 5:09 ` [PATCH v3 1/4] i2c: mpc: use device managed APIs Chris Packham
2021-04-13 12:21 ` Wolfram Sang
2021-04-13 13:31 ` Andy Shevchenko
2021-04-13 13:31 ` Andy Shevchenko
2021-04-13 5:09 ` [PATCH v3 2/4] i2c: mpc: Interrupt driven transfer Chris Packham
2021-04-13 12:22 ` Wolfram Sang [this message]
2021-04-13 13:52 ` Andy Shevchenko
2021-04-13 22:28 ` Chris Packham
2021-04-13 23:23 ` Chris Packham
2021-04-13 5:09 ` [PATCH v3 3/4] i2c: mpc: Remove redundant NULL check Chris Packham
2021-04-13 12:27 ` Wolfram Sang
2021-04-13 5:09 ` [PATCH v3 3/3] MAINTAINERS: Add Chris Packham as FREESCALE MPC I2C maintainer Chris Packham
2021-04-13 5:14 ` Chris Packham
2021-04-13 11:19 ` Andy Shevchenko
2021-04-13 5:09 ` [PATCH v3 4/4] " Chris Packham
2021-04-13 12:27 ` Wolfram Sang
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=20210413122258.GC1553@kunai \
--to=wsa@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).