From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
openipmi-developer@lists.sourceforge.net
Subject: [PATCH RFC 0/3] treewide: remove open coded SMBus block transfers
Date: Tue, 12 Jan 2021 17:41:26 +0100 [thread overview]
Message-ID: <20210112164130.47895-1-wsa+renesas@sang-engineering.com> (raw)
The bigger picture is that I want to extend the maximum block length for
SMBus block transfers from 32 (SMBus2) to 255 (SMBus3). That needs some
cleanups and refactoring first. To make that easier, it would be helpful
if all in-kernel users would call the helper functions of the I2C core
for SMBus block transfers and not open code it via the generic
smbus_xfer.
This series converts the three users doing that. I don't have the
hardware, so these patches are only build tested. Please let me know
what you think.
Wolfram Sang (3):
media: i2c: adv7842: remove open coded version of SMBus block write
media: i2c: adv7842: remove open coded version of SMBus block read
ipmi: remove open coded version of SMBus block write
drivers/char/ipmi/ipmb_dev_int.c | 21 +++++++----------
drivers/media/i2c/adv7511-v4l2.c | 40 +++++++++++---------------------
drivers/media/i2c/adv7842.c | 14 +----------
3 files changed, 23 insertions(+), 52 deletions(-)
--
2.29.2
next reply other threads:[~2021-01-12 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 16:41 Wolfram Sang [this message]
2021-01-12 16:41 ` [PATCH RFC 1/3] media: i2c: adv7842: remove open coded version of SMBus block write Wolfram Sang
2021-01-18 9:24 ` Hans Verkuil
2021-01-18 9:32 ` Wolfram Sang
2021-01-12 16:41 ` [PATCH RFC 2/3] media: i2c: adv7842: remove open coded version of SMBus block read Wolfram Sang
2021-01-12 16:44 ` Wolfram Sang
2021-01-12 19:41 ` Wolfram Sang
2021-01-18 9:22 ` Hans Verkuil
2021-01-18 9:33 ` Wolfram Sang
2021-01-12 16:41 ` [PATCH RFC 3/3] ipmi: remove open coded version of SMBus block write Wolfram Sang
2021-01-14 0:48 ` Corey Minyard
2021-01-14 14:04 ` 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=20210112164130.47895-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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).