Consistent naming for physical LED.

[Patrick Williams]

On Mon, May 08, 2017 at 10:09:55AM +0000, Rahul Maheshwari3 wrote:
>    Patrick
>    I was believing that these 3 physical LEDs(Identify, Fault, Power) will
>    be lit on/off based on group LED asserted state. Example: Physical's
>    fault LED will be lit ON when any fault LED(e.g. cpu0fault) in group is
>    asserted.
>    If that is not the case and we need to rely on below LED groups to get
>    full system status then - how are we going to display state like blink
>    in future using these group LED?

Specific LED behavior is a system policy that differs by system and
OEM/ODM.  There is not a common set of tests we can create for that.

The groups indicate a virtual function like "the FRU x has a fault" or
"the system is powered on", which may cause an indicator like an LED to
behave in a certain way.  The behavior itself is system specific.  (As
an example, Witherspoon has a front-fault and rear-fault LED that are
both turned 'on' when the system has a fault).

> 
>    /xyz/openbmc_project/led/groups/enclosure_fault
>    /xyz/openbmc_project/led/groups/enclosure_identify
>    /xyz/openbmc_project/led/groups/power_on
>    /xyz/openbmc_project/led/groups/power_off
> 
>    Thanks
>    Rahul
> 
>      ----- Original message -----
>      From: Patrick Williams <patrick at stwcx.xyz>
>      To: Rahul Maheshwari3 <rahulmaheshwari at in.ibm.com>
>      Cc: openbmc at lists.ozlabs.org
>      Subject: Re: Consistent naming for physical LED.
>      Date: Fri, May 5, 2017 11:35 PM
> 
>    On Fri, May 05, 2017 at 09:50:37AM +0000, Rahul Maheshwari3 wrote:
>    >    Hi
>    >    With new xyz interface, I see that physical Identify LED is named
>    >    differently as "id" in Witherspoon and system state led as "beep"
>    in
>    >    Barreleye. Also I see that we have 3rd LED in Witherspoon is
>    "fault"
>    >    (for enclosure fault) and in Barreleye and palmetto "heartbeat"
>    (for
>    >    BMC state state).
>    >
>    >    Can we have same set of name/xyz url for physical LED across
>    different
>    >    systems?
>    >
>    >    Witherspoon
>    >        "/xyz/openbmc_project/led/physical/power",         System
>    State LED
>    >        "/xyz/openbmc_project/led/physical/id",
>    Identify LED
>    >        "/xyz/openbmc_project/led/physical/fault"
>    Enclosure
>    >    fault LED
>    >    Barreleye
>    >        "/xyz/openbmc_project/led/physical/identify",        Identify
>    LED
>    >        "/xyz/openbmc_project/led/physical/beep",           System
>    State
>    >    LED
>    >        "/xyz/openbmc_project/led/physical/heartbeat"     BMC state
>    >    Palmetto
>    >        "/xyz/openbmc_project/led/physical/power",         System
>    state
>    >        "/xyz/openbmc_project/led/physical/identify",        Identify
>    LED
>    >        "/xyz/openbmc_project/led/physical/heartbeat"     BMC state
>    >
>    >    Thanks
>    >    Rahul
>    Rahul,
>    We expect those to potentially be generated from board schematics and
>    are not intended to be used as a universal identifier for anything.  We
>    do have requirements on the naming of the LED groups, which is what we
>    intend users to interact with.  What are you trying to use the physical
>    LED for that you would like some kind of consistent naming and are you
>    sure the group would not be more appropriate for your purpose?
>    --
>    Patrick Williams

-- 
Patrick Williams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Digital signature
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170531/23f63629/attachment-0001.sig>