From: Aaron Sierra <asierra-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
To: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Christian Gmeiner
<christian.gmeiner-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Jean Delvare <jdelvare-IBi9RG/b67k@public.gmane.org>
Subject: Re: [PATCH 3/3] at24: Support 16-bit devices on SMBus
Date: Thu, 3 Sep 2015 17:20:43 -0500 (CDT) [thread overview]
Message-ID: <1314711793.101617.1441318843659.JavaMail.zimbra@xes-inc.com> (raw)
In-Reply-To: <361739546.82254.1441310010061.JavaMail.zimbra-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
----- Original Message -----
> From: "Aaron Sierra" <asierra-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
> Sent: Thursday, September 3, 2015 2:53:30 PM
>
> 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.
>
> This patch introduces at24_smbus_read_byte_data to transparently handle
> single-byte reads from 8-bit and 16-bit devices.
>
> Functionality has been tested with the following devices:
>
> AT24CM01 attached to Intel ISCH SMBus (1.8 KB/s)
> AT24C512 attached to Intel I801 SMBus (1.4 KB/s)
>
> Signed-off-by: Nate Case <ncase-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
> Signed-off-by: Aaron Sierra <asierra-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
> ---
> drivers/misc/eeprom/Kconfig | 4 +++-
> drivers/misc/eeprom/at24.c | 40 +++++++++++++++++++++++++++++++++++-----
> 2 files changed, 38 insertions(+), 6 deletions(-)
All,
Shortly after submitting, I found that there are conflicts between this
patch and activity in i2c/for-next. Specifically with this patch:
eeprom: at24: use i2c_smbus_read_i2c_block_data_or_emulated
Patches 1/3 and 2/3 don't have conflicts. I've reworked this patch (3/3)
and retested on top of i2c/for-next. Should I submit all three patches
as v2 or wait for the first two to be reviewed?
-Aaron
next prev parent reply other threads:[~2015-09-03 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1001500768.63909.1441302107931.JavaMail.zimbra@xes-inc.com>
[not found] ` <1001500768.63909.1441302107931.JavaMail.zimbra-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
2015-09-03 19:53 ` [PATCH 3/3] at24: Support 16-bit devices on SMBus Aaron Sierra
[not found] ` <361739546.82254.1441310010061.JavaMail.zimbra-AQeFf1F/bRxBDgjK7y7TUQ@public.gmane.org>
2015-09-03 22:20 ` Aaron Sierra [this message]
2015-09-21 18:40 ` [PATCH 3/3 v2] " Aaron Sierra
2015-11-03 10:33 ` [PATCH 3/3] " Jean Delvare
2015-11-03 20:20 ` Aaron Sierra
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=1314711793.101617.1441318843659.JavaMail.zimbra@xes-inc.com \
--to=asierra-aqeff1f/brxbdgjk7y7tuq@public.gmane.org \
--cc=christian.gmeiner-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jdelvare-IBi9RG/b67k@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@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