From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Subject: [PATCH 0/8] i2c: improve RECV_LEN documentation & usage
Date: Sat, 9 Jan 2021 13:43:04 +0100 [thread overview]
Message-ID: <20210109124314.27466-1-wsa+renesas@sang-engineering.com> (raw)
Because I want to clarify I2C_M_RECV len usage, this series updates the
documentation and some of its users. Patch 1 refactors the whole
documentation of 'i2c_msg', so all usage of I2C_M_* flags and their
conditions hopefully become clearer. Patch 2+3 remove some obvious
boilerplate in the UAPI headers while here. Patch 4 is a driver fix I
found while working on this series. Patch 5 introduces a new convenience
macro to enable SMBus transfers which need I2C_M_RECV_LEN. Then, some
drivers use the new macro, sometimes to remove boilerplate, sometimes
because these SMBus transfers have been forgotten before.
This series is the first part of a larger work to extend I2C_M_RECV_LEN
to allow larger transfer sizes (as specified in the SMBus 3.0 standard)
and to enable this on Renesas R-Car hardware.
Looking forward to comments and/or reviews; the driver patches are only
build-tested.
Happy hacking,
Wolfram
Wolfram Sang (8):
i2c: refactor documentation of struct i2c_msg
i2c: remove licence boilerplate from main UAPI header
i2c: remove licence boilerplate from i2c-dev UAPI header
i2c: octeon: check correct size of maximum RECV_LEN packet
i2c: uapi: add macro to describe support for all SMBus transfers
i2c: algo: bit: use new macro to specifiy capabilities
i2c: qup: advertise SMBus transfers using RECV_LEN
i2c: s3c2410: advertise SMBus transfers using RECV_LEN
drivers/i2c/algos/i2c-algo-bit.c | 4 +-
drivers/i2c/busses/i2c-octeon-core.c | 2 +-
drivers/i2c/busses/i2c-qup.c | 2 +-
drivers/i2c/busses/i2c-s3c2410.c | 2 +-
include/uapi/linux/i2c-dev.h | 25 ++----
include/uapi/linux/i2c.h | 128 ++++++++++++++-------------
6 files changed, 76 insertions(+), 87 deletions(-)
--
2.29.2
next reply other threads:[~2021-01-09 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 12:43 Wolfram Sang [this message]
2021-01-09 12:43 ` [PATCH 8/8] i2c: s3c2410: advertise SMBus transfers using RECV_LEN Wolfram Sang
2021-01-22 9:02 ` [PATCH 0/8] i2c: improve RECV_LEN documentation & usage 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=20210109124314.27466-1-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-samsung-soc@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).