From: Jean Delvare <jdelvare@suse.de>
To: Linux I2C <linux-i2c@vger.kernel.org>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Wolfram Sang <wsa@the-dreams.de>
Subject: Support of DDR4 EEPROMs
Date: Fri, 10 Nov 2017 10:14:16 +0100 [thread overview]
Message-ID: <20171110101416.14410124@endymion> (raw)
Hi all,
My topic for SUSE Hackweek 16 is to add support for DDR4 memory modules
to decode-dimms:
https://hackweek.suse.com/16/projects/add-support-for-ddr4-to-decode-dimms
I naively thought it would only be about modifying the perl script to
decode new fields and new values from the SPD EEPROM, however it turns
out that the EEPROM themselves are different. Instead of regular
24C02-style 256-byte EEPROMs, DDR4 memory modules use 512-byte EEPROMs.
The trick is that they still use only 1 I2C address each in the
0x50-0x57 range. You have to tinker with special commands in the
0x30-0x37 range to select one of 2 256-byte pages that will be
reachable through the 0x50-0x57 I2C address. And as far as I can, it
switched all EEPROMs at once, which won't be easy to implement.
The standard in question is JEDEC EE1004. I'm not sure if we should add
support to the at24 driver, or write a separate driver for such
EEPROMs. Before I start working on that, I would like to ask if anybody
is already working on it?
Thanks,
--
Jean Delvare
SUSE L3 Support
next reply other threads:[~2017-11-10 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 9:14 Jean Delvare [this message]
2017-11-18 18:05 ` Support of DDR4 EEPROMs 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=20171110101416.14410124@endymion \
--to=jdelvare@suse.de \
--cc=bgolaszewski@baylibre.com \
--cc=linux-i2c@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;
as well as URLs for NNTP newsgroup(s).