linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Stephen Horvath <s.horvath@outlook.com.au>
Cc: Jean Delvare <jdelvare@suse.de>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Kamil Aronowski <kamil.aronowski@3mdeb.com>,
	Darsey Litzenberger <dlitz@dlitz.net>,
	Brigham Campbell <me@brighamcampbell.com>
Subject: Re: [PATCH i2c-tools v4 0/8] decode-dimms: Implement DDR5 decoding
Date: Sun, 8 Nov 2026 14:51:32 +0100	[thread overview]
Message-ID: <avB-ZAfbTW_ZDLOV@shikoro> (raw)
In-Reply-To: <20260723-ddr5-v4-0-d7cf78ebbbaf@outlook.com.au>

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

Hi Stephen, all,

On Thu, Jul 23, 2026 at 01:40:11PM +0000, Stephen Horvath wrote:
> Hi, this series of patches adds DDR5 support to decode-dimms.
> 
> I'm not too experienced with perl or the JEDEC specs, so there's
> probably going to be some questionable choices here, but I'd love to
> hear feedback.
> 
> The first 4 patches (1, 2, 3, 4) add the essential DDR5 information to
> decode-dimms.
> 
> The patches 5 & 7 haven't been tested on hardware implementations so I'm
> happy for them to be dropped if they're not useful. However they add
> type specific information and error log support.
> 
> Patch 8 adds XMP and EXPO support for DDR5, though I don't have access
> to the datasheet for either, so I'm fine if they get dropped as well.
> Though I may also implement XMP for DDR3 and DDR4 in another series if
> these are well received.
> 
> Patch 6 just adds a new function `prints2`, to print a subheading,
> used for the error logs, XMP and EXPO.
> 
> Signed-off-by: Stephen Horvath <s.horvath@outlook.com.au>

Thank you so much for the new version! I would really like to include
this in the next i2c-tools version, hopefully this year. This is the
last "blocker". But being zero familiar with the topic, I really need
help. Reviews would be most awesome, of course. But if nobody has time
for that, test reports would also be super helpful. Sadly, I don't even
have DDR5 here.

So, anyone interested in helping?

Happy hacking,

   Wolfram


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

      parent reply	other threads:[~2026-11-08 13:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23 13:40 [PATCH i2c-tools v4 0/8] decode-dimms: Implement DDR5 decoding Stephen Horvath
2026-07-23 13:40 ` [PATCH i2c-tools v4 2/8] decode-dimms: Decode DDR5 Manufacturer Data Stephen Horvath
2026-07-23 13:40 ` [PATCH i2c-tools v4 1/8] decode-dimms: Implement DDR5 checksum parsing Stephen Horvath
2026-07-23 13:40 ` [PATCH i2c-tools v4 3/8] decode-dimms: Decode timings and other data for DDR5 Stephen Horvath
2026-07-23 13:40 ` [PATCH i2c-tools v4 4/8] decode-dimms: Decode DDR5 common module information Stephen Horvath
2026-07-23 13:40 ` [PATCH i2c-tools v4 5/8] decode-dimms: Add basic decoding of type specific information for DDR5 Stephen Horvath
2026-07-23 13:40 ` [PATCH i2c-tools v4 6/8] decode-dimms: Add second level separator Stephen Horvath
2026-07-23 13:40 ` [PATCH i2c-tools v4 7/8] decode-dimms: Decode DDR5 error log Stephen Horvath
2026-07-23 13:40 ` [PATCH i2c-tools v4 8/8] decode-dimms: Add DDR5 XMP 3.0 and EXPO decoding Stephen Horvath
2026-11-08 13:51 ` Wolfram Sang [this message]

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=avB-ZAfbTW_ZDLOV@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=dlitz@dlitz.net \
    --cc=jdelvare@suse.de \
    --cc=kamil.aronowski@3mdeb.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=me@brighamcampbell.com \
    --cc=s.horvath@outlook.com.au \
    /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).