openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: Michael Shen <gpgpgp@google.com>
Cc: openbmc@lists.ozlabs.org
Subject: Re: Propose a new application for reading DIMM SPD directly
Date: Tue, 8 Feb 2022 01:11:29 -0600	[thread overview]
Message-ID: <YgIXodbEP9hmae6Q@heinlein> (raw)
In-Reply-To: <CAD1rtg8sa2OG4jUL8x7Gr9ExzH-tEswhHwSDaZtWhcAN4sAvuw@mail.gmail.com>

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

On Tue, Feb 08, 2022 at 01:10:37PM +0800, Michael Shen wrote:
> Hi Openbmc,
> 
> We would like to propose an application that directly reads the DIMM
> SPD over HW interface(mostly I2C/I3C).

Who is "we"?

> If I understand correctly, the main method for obtaining the SPD
> information in openbmc is from SMBIOS which is prepared by BIOS. And
> We are exploring another way that excludes the involvement of BIOS.

Unless you're proposing that the BIOS itself comes to the BMC to get the SPD
data, I'm somewhat surprised you could come up with a hardware design to make
this work.  Due to the number of DIMM channels and the limited number of CS pins
on JEDEC DIMMs, you're going to have muxes on the bus somewhere.  Mixing muxes
and multi-master access is pretty problematic.  Either the BIOS and BMC are
fighting over the mux, which is going to mess with the mux driver's view of the
world, or you've got one mux for each in which case you're switching masters
onto a bus, which violates a few i2c design rules.

> The architecture of this application will be similar to the
> openbmc/smbios-mdr (the dimm part). The main difference will be the
> data source (changed from SMBIOS to SPD).
> 
> Currently the code is still being implemented, and we plan to support
> DDR5 SPD first, then expand to other DDR generation(if needed).

Hopefully you're leveraging the existing kernel drivers for reading SPD EEPROMs.
This creates you a sysfs file containing the whole of the EEPROM content.  You'd
just need to write a parser for JEDEC SPD format data.

You should take a look at what is already existing in fru-device (part of
entity-manager repository).  This is already doing this for IPMI-format EEPROM
data.  We should be able to replicate/enhance this code, in the same repository,
to handle SPD format.

> If this proposal looks good to you, please help to create a repo for
> this application.
> 
> Best,
> Michael

-- 
Patrick Williams

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

  reply	other threads:[~2022-02-08  7:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08  5:10 Propose a new application for reading DIMM SPD directly Michael Shen
2022-02-08  7:11 ` Patrick Williams [this message]
2022-02-08  8:23   ` Michael Shen
2022-02-09 19:56     ` Patrick Williams
2022-02-09 20:20       ` Ed Tanous
2022-02-09 21:14         ` Patrick Williams
2022-02-09 22:45           ` Ed Tanous
2022-02-11  0:40             ` Michael Shen
2022-02-11 21:21               ` Zbigniew, Lukwinski
2022-02-14 22:17                 ` Benjamin Fair
2022-02-15  1:50                   ` Michael Shen
2022-02-15 20:39                     ` Zbigniew, Lukwinski
2022-02-17  3:59                       ` Michael Shen
2022-02-21 12:07                         ` Zbigniew, Lukwinski

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=YgIXodbEP9hmae6Q@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=gpgpgp@google.com \
    --cc=openbmc@lists.ozlabs.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).