From: Peter Korsgaard <peter@korsgaard.com>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: Wolfram Sang <wsa@the-dreams.de>,
linux-i2c <linux-i2c@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH 0/9] eeprom: at24: at24cs series serial number read
Date: Wed, 21 Oct 2015 13:03:36 +0200 [thread overview]
Message-ID: <87bnbsiiuv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1445330607-12470-1-git-send-email-bgolaszewski@baylibre.com> (Bartosz Golaszewski's message of "Tue, 20 Oct 2015 10:43:18 +0200")
>>>>> "Bartosz" == Bartosz Golaszewski <bgolaszewski@baylibre.com> writes:
> 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.
> This series adds support for reading the serial number through a sysfs
> attribute.
> While we're at it: some of the patches contain readability tweaks and code
> organization fixes.
> Tested with at24cs64 and at24cs02 chips (for both 16 and 8 bit address
> pointers).
As the serial number is available on a separate i2c address, wouldn't
it be simpler to handle these as special (read only) device variants and
instantiate E.G. a 24c64 (for the normal data) and a 24cs64 (for the
serial)?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-10-21 11:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 8:43 Bartosz Golaszewski
2015-10-20 8:43 ` [RESEND PATCH 1/9] eeprom: at24: platform_data: use BIT() macro Bartosz Golaszewski
2015-10-20 8:43 ` [RESEND PATCH 2/9] eeprom: at24: new flag in platform_data Bartosz Golaszewski
2015-10-20 8:43 ` [RESEND PATCH 3/9] eeprom: at24: tie up an additional address for at24cs series Bartosz Golaszewski
2015-10-20 8:43 ` [RESEND PATCH 4/9] eeprom: at24: support reading of the serial number Bartosz Golaszewski
2015-10-20 8:43 ` [RESEND PATCH 5/9] eeprom: at24: export the serial number through sysfs Bartosz Golaszewski
2015-10-20 8:43 ` [RESEND PATCH 6/9] eeprom: at24: improve the device_id table readability Bartosz Golaszewski
2015-10-20 8:43 ` [RESEND PATCH 7/9] eeprom: at24: add the at24cs series to the list of supported devices Bartosz Golaszewski
2015-10-20 8:43 ` [RESEND PATCH 8/9] eeprom: at24: remove a reduntant if Bartosz Golaszewski
2015-10-20 8:43 ` [RESEND PATCH 9/9] eeprom: at24: readability tweaks Bartosz Golaszewski
2015-10-21 11:03 ` Peter Korsgaard [this message]
2015-10-21 14:15 ` [RESEND PATCH 0/9] eeprom: at24: at24cs series serial number read Bartosz Golaszewski
2015-10-21 14:23 ` Peter Korsgaard
2015-10-21 14:42 ` Bartosz Golaszewski
2015-10-21 15:08 ` Peter Korsgaard
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=87bnbsiiuv.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=bgolaszewski@baylibre.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®