FRU Device type one byte or Two byte Validation

[Andrei Kartashev]

> 
> > 
> > > > 
> > > >        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