From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Irina Tirdea <irina.tirdea-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC PATCH 1/1] i2c: core: Add support for best effort block read emulation
Date: Wed, 15 Apr 2015 17:55:10 +0200 [thread overview]
Message-ID: <20150415155510.GB914@katana> (raw)
In-Reply-To: <1427294000-32406-1-git-send-email-irina.tirdea-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 4274 bytes --]
On Wed, Mar 25, 2015 at 04:33:20PM +0200, Irina Tirdea wrote:
> There are devices that need to handle block transactions
> regardless of the capabilities exported by the adapter.
> For performance reasons, they need to use i2c read blocks
> if available, otherwise emulate the block transaction with word
> or byte transactions.
>
> Add support for a helper function that would read a data block
> using the best transfer available: I2C_FUNC_SMBUS_READ_I2C_BLOCK,
> I2C_FUNC_SMBUS_READ_WORD_DATA or I2C_FUNC_SMBUS_READ_BYTE_DATA.
>
> Signed-off-by: Irina Tirdea <irina.tirdea-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> ---
>
> Hi,
>
> This is a new API proposal to handle i2c block emulation in the
> core instead of the driver code.
>
> This is needed for a set of iio sensor changes ([1], [2], [3])
> that would otherwise duplicate this code. There are also some
> usages of this functionality in the kernel (e.g. eeprom driver at24).
>
> Please let me know what you think.
I am open to add something like this. One change I'd like to request is
to introduce a user, e.g. convert at24.
>
> Thanks,
> Irina
>
> [1] https://lkml.org/lkml/2015/2/16/408
> [2] https://lkml.org/lkml/2015/2/16/413
> [3] https://lkml.org/lkml/2015/2/16/402
>
> drivers/i2c/i2c-core.c | 62 ++++++++++++++++++++++++++++++++++++++++++++++++++
> include/linux/i2c.h | 3 +++
> 2 files changed, 65 insertions(+)
>
> diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
> index fe80f85..2579f7d 100644
> --- a/drivers/i2c/i2c-core.c
> +++ b/drivers/i2c/i2c-core.c
> @@ -2907,6 +2907,68 @@ trace:
> }
> EXPORT_SYMBOL(i2c_smbus_xfer);
>
> +/**
> + * i2c_smbus_read_i2c_block_data_or_emulated - read block or emulate
> + * @client: Handle to slave device
> + * @command: Byte interpreted by slave
> + * @length: Size of data block; SMBus allows at most 32 bytes
> + * @values: Byte array into which data will be read; big enough to hold
> + * the data returned by the slave. SMBus allows at most 32 bytes.
Sidenote: SMBus3 allows 255 byte, but we don't support that (yet), so
this is okay for now.
> + *
> + * This executes the SMBus "block read" protocol if supported by the adapter.
> + * If block read is not supported, it emulates it using either word or byte
> + * read protocols depending on availability.
Here I'd like to see a warning that people should double-check if their
I2C slave does support that. Sometimes one can't exchange a block
transfer with a byte transfer.
> + */
> +s32 i2c_smbus_read_i2c_block_data_or_emulated(const struct i2c_client *client,
> + u8 command, u8 length, u8 *values)
> +{
> + u8 i;
> + int status;
> +
> + if (length > I2C_SMBUS_BLOCK_MAX)
> + length = I2C_SMBUS_BLOCK_MAX;
> +
> + if (i2c_check_functionality(client->adapter,
> + I2C_FUNC_SMBUS_READ_I2C_BLOCK)) {
> + return i2c_smbus_read_i2c_block_data(client, command,
> + length, values);
> + } else if (i2c_check_functionality(client->adapter,
> + I2C_FUNC_SMBUS_READ_WORD_DATA |
> + I2C_FUNC_SMBUS_READ_BYTE_DATA)) {
What about skipping the need for READ_BYTE_DATA and dump the byte which
was maybe read too much?
> + for (i = 0; (i + 2) <= length; i += 2) {
> + status = i2c_smbus_read_word_data(client, command + i);
> + if (status < 0)
> + return status;
> + values[i] = status & 0xff;
> + values[i+1] = status >> 8;
> + }
> + if (i < length) {
> + status = i2c_smbus_read_byte_data(client, command + i);
> + if (status < 0)
> + return status;
> + values[i] = status;
> + i++;
> + }
> + return i;
> + } else if (i2c_check_functionality(client->adapter,
> + I2C_FUNC_SMBUS_READ_BYTE_DATA)) {
> + for (i = 0; i < length; i++) {
> + status = i2c_smbus_read_byte_data(client, command + i);
> + if (status < 0)
> + return status;
> + values[i] = status;
> + }
> + return i;
> + }
> +
> + dev_err(&client->adapter->dev, "Unsupported transactions: %d,%d,%d\n",
> + I2C_SMBUS_I2C_BLOCK_DATA, I2C_SMBUS_WORD_DATA,
> + I2C_SMBUS_BYTE_DATA);
> +
> + return -EOPNOTSUPP;
> +}
> +EXPORT_SYMBOL(i2c_smbus_read_i2c_block_data_or_emulated);
Thanks,
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-15 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-25 14:33 [RFC PATCH 1/1] i2c: core: Add support for best effort block read emulation Irina Tirdea
[not found] ` <1427294000-32406-1-git-send-email-irina.tirdea-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-04-15 15:55 ` Wolfram Sang [this message]
2015-04-17 13:32 ` Tirdea, Irina
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=20150415155510.GB914@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=irina.tirdea-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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