linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: linux-i2c <linux-i2c@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	srinivas.kandagatla@linaro.org, maxime.ripard@free-electrons.com,
	Andrew Lunn <andrew@lunn.ch>
Subject: Re: [RESEND PATCH v2 00/13] eeprom: support for at24cs and at24mac
Date: Sat, 16 Apr 2016 23:17:33 +0200	[thread overview]
Message-ID: <20160416211733.GD1522@katana> (raw)
In-Reply-To: <1460401049-25459-1-git-send-email-bgolaszewski@baylibre.com>

[-- Attachment #1: Type: text/plain, Size: 1859 bytes --]

Hi,

On Mon, Apr 11, 2016 at 11:57:16AM -0700, Bartosz Golaszewski wrote:
> Chips from the at24cs EEPROM series have an additional read-only
> memory area containing a factory pre-programmed serial number. In
> order to access it, a dummy write must be executed before reading
> the serial number bytes.
> 
> Chips from the at24mac familiy, apart from the serial number, have
> a second special memory area containing a factory programmed
> EUI-48/EUI64 mac address.
> 
> The read-only serial/mac memory area is accessible on a different i2c
> slave address (addr + 0x08). This patchset makes it possible to
> instantiate a separate at24 device on this second address and access
> the read-only area through the regular eeprom sysfs attribute or the
> new nvmem subsystem.
> 
> This series also contains several patches intoducing some minor tweaks
> and refactoring.
> 
> Tested with at24cs32 and at24cs02 chips (for both 16 and 8 bit address
> pointers). I have no means of testing the support for at24mac chips, I
> relied solely on the datasheet.

Thanks for adding at24mac nonetheless!

I still don't understand why you want to add this to at24 instead of
doing a seperate driver for it? You basically tie a read_function to an
nvmem device. You don't need the special smbus handling, cutting large
requests into chunks, write support, size flags and all this from at24.
And with the function pointers, it makes the already complex code a bit
more complex.

IMO, this could be solved by a simple, seperate driver. You could start
with at24 and remove unneeded stuff. I think there should be mainly
nvmem-init code and your read routines left. I also think this new
driver should be allowed to set the "compat" option of the nvmem
framework, so you'll get the "eeprom" file, too.

Or am I overlooking something?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-04-16 21:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 18:57 [RESEND PATCH v2 00/13] eeprom: support for at24cs and at24mac Bartosz Golaszewski
2016-04-11 18:57 ` [RESEND PATCH v2 01/13] eeprom: at24: remove a reduntant if Bartosz Golaszewski
2016-04-16 20:48   ` Wolfram Sang
2016-04-11 18:57 ` [RESEND PATCH v2 02/13] eeprom: at24: improve the device_id table readability Bartosz Golaszewski
2016-04-11 18:57 ` [RESEND PATCH v2 03/13] eeprom: at24: platform_data: use BIT() macro Bartosz Golaszewski
2016-04-11 18:57 ` [RESEND PATCH v2 04/13] eeprom: at24: make locking more fine-grained Bartosz Golaszewski
2016-04-16 20:56   ` Wolfram Sang
2016-05-03 17:55     ` Bartosz Golaszewski
2016-04-11 18:57 ` [RESEND PATCH v2 05/13] eeprom: at24: replace msleep() with usleep_range() Bartosz Golaszewski
2016-04-16 20:58   ` Wolfram Sang
2016-04-11 18:57 ` [RESEND PATCH v2 06/13] eeprom: at24: add serial number flag Bartosz Golaszewski
2016-04-11 18:57 ` [RESEND PATCH v2 07/13] eeprom: at24: support reading of the serial number Bartosz Golaszewski
2016-04-11 18:57 ` [RESEND PATCH v2 08/13] eeprom: at24: call read and write routines via function pointers Bartosz Golaszewski
2016-04-11 18:57 ` [RESEND PATCH v2 09/13] eeprom: at24: use at24cs_serial_read() Bartosz Golaszewski
2016-04-11 18:57 ` [RESEND PATCH v2 10/13] eeprom: at24: add the at24cs series to the list of supported devices Bartosz Golaszewski
2016-04-11 18:57 ` [RESEND PATCH v2 11/13] eeprom: at24: add at24mac series flag Bartosz Golaszewski
2016-04-11 18:57 ` [RESEND PATCH v2 12/13] eeprom: at24: add support for at24mac series Bartosz Golaszewski
2016-04-11 18:57 ` [RESEND PATCH v2 13/13] eeprom: at24: add at24mac chips to the list of supported devices Bartosz Golaszewski
2016-04-16 21:17 ` Wolfram Sang [this message]
2016-04-20 14:38   ` [RESEND PATCH v2 00/13] eeprom: support for at24cs and at24mac Bartosz Golaszewski
2016-05-02  7:42     ` 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=20160416211733.GD1522@katana \
    --to=wsa@the-dreams.de \
    --cc=andrew@lunn.ch \
    --cc=bgolaszewski@baylibre.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=srinivas.kandagatla@linaro.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).