linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: [PATCH v2] eeprom: at24: fix reading from 24MAC402/24MAC602
Date: Mon, 27 Nov 2017 20:59:20 +0100	[thread overview]
Message-ID: <9f1ca504-9382-1fce-7750-433b6d5078bb@gmail.com> (raw)
In-Reply-To: <32cfbfe3-fdff-5165-2753-186cbe2055a4@gmail.com>

Am 27.11.2017 um 20:46 schrieb Heiner Kallweit:
> Chip datasheet mentions that word addresses other than the actual
> start position of the MAC delivers undefined results. So fix this.
> Current implementation doesn't work due to this wrong offset.
> 
> Fixes: 0b813658c115 "eeprom: at24: add support for at24mac series"
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
> v2:
> - extended commit message
> ---
>  drivers/misc/eeprom/at24.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/misc/eeprom/at24.c b/drivers/misc/eeprom/at24.c
> index e0b4b36ef..00d602be7 100644
> --- a/drivers/misc/eeprom/at24.c
> +++ b/drivers/misc/eeprom/at24.c
> @@ -425,7 +425,8 @@ static ssize_t at24_eeprom_read_mac(struct at24_data *at24, char *buf,
>  	memset(msg, 0, sizeof(msg));
>  	msg[0].addr = client->addr;
>  	msg[0].buf = addrbuf;
> -	addrbuf[0] = 0x90 + offset;
> +	/* EUI-48 starts from 0x9a, EUI-64 from 0x98 */
> +	addrbuf[0] = 0xa0 - at24->chip.byte_len + offset;
>  	msg[0].len = 1;
>  	msg[1].addr = client->addr;
>  	msg[1].flags = I2C_M_RD;
> 
Are you going to apply this patch also before my other patch series?
Then I will consider this too when re-basing.

  reply	other threads:[~2017-11-27 19:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 19:46 [PATCH v2] eeprom: at24: fix reading from 24MAC402/24MAC602 Heiner Kallweit
2017-11-27 19:59 ` Heiner Kallweit [this message]
2017-11-27 20:07   ` Heiner Kallweit
2017-11-27 21:10     ` Bartosz Golaszewski
2017-11-27 21:47       ` Heiner Kallweit
2017-11-29 14:57 ` Bartosz Golaszewski

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=9f1ca504-9382-1fce-7750-433b6d5078bb@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=brgl@bgdev.pl \
    --cc=linux-i2c@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).