You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there are state sensors with state set ID IdentifyState.
1.Lookup the FRU object associated with the sensor
2.Create the LED D-Bus object /xyz/openbmc_project/led/groups/ object
3.PLDM daemon implements the xyz.openbmc_project.Association.Definitions to create association between FRU and LED D-Bus objects
4.Initialize the Identify D-Bus property by issuing GetSensorReading
5.Add this sensor to the PlatformEventMessage map to update D-bus property value when the PHYP detects a change
If there is a state effecter with the identify state to the corresponding FRU bind the SetProperty of the LED to a StateSetEffecter on the corresponding effecter.
The text was updated successfully, but these errors were encountered:
nmuruli
changed the title
PLDM: Process the Host PDRs for the state sensors & effecters with state set ID IdentifyState
PLDM: (MEX LED) Process the Host PDRs for the state sensors & effecters with state set ID IdentifyState
Apr 30, 2021
Could you kindly explain this issue?
I have a couple of questions:
PLDM daemon needs to create /xyz/openbmc_project/led/groups/<name>? If so, What is the difference between this and the phosphor-led-manager service ?
If there is a state effecter with the identify state to the corresponding FRU bind the SetProperty of the LED to a StateSetEffecter on the corresponding effecter.
Could you kindly explain this issue?
I have a couple of questions:
1. PLDM daemon needs to create ` /xyz/openbmc_project/led/groups/<name>`? If so, What is the difference between this and the `phosphor-led-manager` service ?
Any dbus object can be hosted by any services, its not always the case that led objects should be created by led-manager. In this case the led- objects are created by pldm, based on whether the set set ID identify state is implemented on those state sensors.
2. > If there is a state effecter with the identify state to the corresponding FRU bind the SetProperty of the LED to a StateSetEffecter on the corresponding effecter.
sorry, I do not understand?
once , pldm hosts the led group object, we will have to implement the set and get operations of the Asserted Property.
When some one sets the Asserted dbus property, I think we need to map the effecter that implements the identity led state set ,& call SetEffecterStates command with the right effecter, so that the LED on the MEX will be on.
If there are state sensors with state set ID IdentifyState.
1.Lookup the FRU object associated with the sensor
2.Create the LED D-Bus object /xyz/openbmc_project/led/groups/ object
3.PLDM daemon implements the xyz.openbmc_project.Association.Definitions to create association between FRU and LED D-Bus objects
4.Initialize the Identify D-Bus property by issuing GetSensorReading
5.Add this sensor to the PlatformEventMessage map to update D-bus property value when the PHYP detects a change
If there is a state effecter with the identify state to the corresponding FRU bind the SetProperty of the LED to a StateSetEffecter on the corresponding effecter.
The text was updated successfully, but these errors were encountered: