From: Andrei Kartashev <a.kartashev@yadro.com>
To: <openbmc@lists.ozlabs.org>
Subject: Re: FRU Device type one byte or Two byte Validation
Date: Mon, 29 Nov 2021 21:36:41 +0300 [thread overview]
Message-ID: <c38c58809e2ab0327e303779fe154444d44b654a.camel@yadro.com> (raw)
In-Reply-To: <CAH2-KxD5G-+7F8d9xpCtE-ajdKyMiAUWy0zXvfk3=a+TFtrztw@mail.gmail.com>
>
> >
> > > >
> > > > We wanted to interlink this logic with entity-manager code
> > > > to get the device type.
> > > >
> > > > Could you please provide the suggestions on get the device
> > > > type in entity-manager.
> > >
> > > Entity-manager provides the exposes records on dbus, for which
> > > reactors can pick them up and use them.
> >
> >
> > Is there any way to get the dynamic values (device type - 8bit/16bit
> > ) from the machine layer
> > to the entity-manager ?
>
Just an idea came to mind:
This likely would not help in this case, but for situations when we
know in advance that on particular I2C bus/address there can be only
8bit or 16bit FRU EEPROM, we can avoid autodetection by having
configuration json file for the FruDevice.
There already was an attempt to introduce config file for FruDevice
here:
https://gerrit.openbmc-project.xyz/c/openbmc/entity-manager/+/40039
And FruDevice already has blacklist json, so we can make more generic
config to have all this configurations.
--
Best regards,
Andrei Kartashev
next prev parent reply other threads:[~2021-11-29 18:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 9:18 FRU Device type one byte or Two byte Validation Kumar Thangavel
2021-11-24 20:40 ` Ed Tanous
2021-11-25 9:08 ` Kumar Thangavel
2021-11-29 17:39 ` Ed Tanous
2021-11-29 18:36 ` Andrei Kartashev [this message]
2021-12-17 13:15 ` Patrick Williams
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=c38c58809e2ab0327e303779fe154444d44b654a.camel@yadro.com \
--to=a.kartashev@yadro.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).