From: Jean Delvare <jdelvare@suse.de>
To: Aaron Sierra <asierra@xes-inc.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org,
Christian Gmeiner <christian.gmeiner@gmail.com>,
Nate Case <ncase@xes-inc.com>
Subject: Re: [PATCH v6] at24: Support SMBus read/write of 16-bit devices
Date: Tue, 17 Nov 2015 17:52:14 +0100 [thread overview]
Message-ID: <20151117175214.73a8cf68@endymion.delvare> (raw)
In-Reply-To: <1637462042.105214.1447718539047.JavaMail.zimbra@xes-inc.com>
On Mon, 16 Nov 2015 18:02:19 -0600 (CST), Aaron Sierra wrote:
> Previously, the at24 driver would bail out in the case of a 16-bit
> addressable EEPROM attached to an SMBus controller. This is because
> SMBus block reads and writes don't map to I2C multi-byte reads and
> writes when the offset portion is 2 bytes.
>
> Instead of bailing out, this patch settles for functioning with single
> byte read SMBus cycles. Writes can be block or single-byte, depending
> on SMBus controller features.
>
> Read access is not without some risk. Multiple SMBus cycles are
> required to read even one byte. If the SMBus has multiple masters and
> one accesses this EEPROM between the dummy address write and the
> subsequent current-address-read cycle(s), this driver will receive
> data from the wrong address.
>
> Functionality has been tested with the following devices:
>
> AT24CM01 attached to Intel ISCH SMBus
> AT24C512 attached to Intel I801 SMBus
>
> Read performance:
> 3.6 KB/s with 32-byte* access
>
> *limited to 32-bytes by I2C_SMBUS_BLOCK_MAX.
>
> Write performance:
> 248 B/s with 1-byte page (default)
> 3.9 KB/s with 128-byte* page (via platform data)
>
> *limited to 31-bytes by I2C_SMBUS_BLOCK_MAX - 1.
>
> Signed-off-by: Nate Case <ncase@xes-inc.com>
> Signed-off-by: Aaron Sierra <asierra@xes-inc.com>
> Reviewed-by: Jean Delvare <jdelvare@suse.de>
> ---
> v2 - Account for changes related to introduction of
> i2c_smbus_read_i2c_block_data_or_emulated()
> v3 - Consolidate three patches into one
> - Expand comments regarding SMBus multi-master read risks.
> - Rely on current-address-read for improved read performance (i.e. one
> dummy address write followed by multiple individual byte reads).
> This improves performance from 1.4 KiB/s to 3.6 KiB/s.
> - Use struct at24_data's writebuf instead of kzalloc-ing
> - Only limit write_max by 1-byte when accessing a 16-bit device with
> block writes instead of attempting to preserve a power-of-two.
> - Style fixes (indentation, parentheses, unnecessary masking, etc.)
> v4 - Address 16-bit safety in Kconfig
> - Set "count" to zero later in at24_smbus_read_block_data()
> - Fix over-80-columns issues in at24_eeprom_read()
> - Fix write_max off-by-one in at24_probe()
> - Check SMBus functionality needed for 16-bit device reads
> - Homogenize indentation of SMBus functionality checks for SMBus write
> v5 - 16-bit device read needs READ_BYTE not READ_BYTE_DATA
> - Clarify write_max limiting with smbus_max
> - Add X-ES copyright
> v6 - Update comment associated with SMBus functionality testing for 16-bit
> device read (READ_BYTE not READ_BYTE_DATA)
>
> drivers/misc/eeprom/Kconfig | 5 +-
> drivers/misc/eeprom/at24.c | 132 +++++++++++++++++++++++++++++++++++++++-----
> 2 files changed, 122 insertions(+), 15 deletions(-)
> (...)
Sweet, thanks for your patience.
Now it's up to Wolfram.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2015-11-17 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1914980865.104978.1447718293775.JavaMail.zimbra@xes-inc.com>
2015-11-17 0:02 ` [PATCH v6] at24: Support SMBus read/write of 16-bit devices Aaron Sierra
2015-11-17 16:52 ` Jean Delvare [this message]
2015-12-11 13:19 ` Wolfram Sang
2015-12-18 19:47 ` Aaron Sierra
2015-12-18 20:53 ` Jean Delvare
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=20151117175214.73a8cf68@endymion.delvare \
--to=jdelvare@suse.de \
--cc=asierra@xes-inc.com \
--cc=christian.gmeiner@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=ncase@xes-inc.com \
--cc=wsa@the-dreams.de \
/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).