From: Chris Packham <chris.packham@alliedtelesis.co.nz>
To: Wolfram Sang <wsa@kernel.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Subject: [PATCH v3 0/4] i2c: mpc: Refactor to improve responsiveness
Date: Tue, 13 Apr 2021 17:09:51 +1200 [thread overview]
Message-ID: <20210413050956.23264-1-chris.packham@alliedtelesis.co.nz> (raw)
This is an update to what is already in i2c/for-next. I've included "i2c: mpc:
use device managed APIs" which had some problems in the remove code path which
Wei Yongjun kindly pointed out with a fix. I've incorporated those changes into
this version in case the original is reverted.
I've tested on T2081 and P2041 based systems with a number of i2c and smbus
devices. Also this time I included a few iterations of module insert/remove
which would have caught the earlier errors.
Chris Packham (4):
i2c: mpc: use device managed APIs
i2c: mpc: Interrupt driven transfer
i2c: mpc: Remove redundant NULL check
MAINTAINERS: Add Chris Packham as FREESCALE MPC I2C maintainer
MAINTAINERS | 7 +
drivers/i2c/busses/i2c-mpc.c | 488 +++++++++++++++++++----------------
2 files changed, 267 insertions(+), 228 deletions(-)
--
2.31.1
next reply other threads:[~2021-04-13 5:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 5:09 Chris Packham [this message]
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
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=20210413050956.23264-1-chris.packham@alliedtelesis.co.nz \
--to=chris.packham@alliedtelesis.co.nz \
--cc=andy.shevchenko@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@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).