Chassis sled cycle

Vijay Khemka vijaykhemka at fb.com
Thu Apr 2 04:28:11 AEDT 2020


Alright, let me look into this design.

From: William Kennington <wak at google.com>
Date: Tuesday, March 31, 2020 at 4:11 PM
To: Vijay Khemka <vijaykhemka at fb.com>
Cc: Benjamin Fair <benjaminfair at google.com>, "jason.m.bills at linux.intel.com" <jason.m.bills at linux.intel.com>, James Feist <james.feist at linux.intel.com>, "openbmc at lists.ozlabs.org" <openbmc at lists.ozlabs.org>
Subject: Re: Chassis sled cycle

You don't really want to implement that logic in the power daemon since it has to find and unbind devices and whatnot. It's quite specific to a platform and well tailored to be scripted.

On Tue, Mar 31, 2020 at 3:58 PM Vijay Khemka <vijaykhemka at fb.com<mailto:vijaykhemka at fb.com>> wrote:
William,
I am not worried by that I am just considering that one has to implement that unit file as well.
Rather than triggering unit file why can’t we trigger gpio or i2c command based on configuration
Provided by each platform.

Regards
-Vijay

From: William Kennington <wak at google.com<mailto:wak at google.com>>
Date: Tuesday, March 31, 2020 at 1:37 PM
To: Vijay Khemka <vijaykhemka at fb.com<mailto:vijaykhemka at fb.com>>
Cc: Benjamin Fair <benjaminfair at google.com<mailto:benjaminfair at google.com>>, "jason.m.bills at linux.intel.com<mailto:jason.m.bills at linux.intel.com>" <jason.m.bills at linux.intel.com<mailto:jason.m.bills at linux.intel.com>>, James Feist <james.feist at linux.intel.com<mailto:james.feist at linux.intel.com>>, "openbmc at lists.ozlabs.org<mailto:openbmc at lists.ozlabs.org>" <openbmc at lists.ozlabs.org<mailto:openbmc at lists.ozlabs.org>>
Subject: Re: Chassis sled cycle

The target is just that file. Platform specific services add themselves as WantedBy. You shouldn't really need to worry about that part as triggering the service will cause them to run.

On Tue, Mar 31, 2020 at 1:33 PM Vijay Khemka <vijaykhemka at fb.com<mailto:vijaykhemka at fb.com>> wrote:


On 3/31/20, 10:53 AM, "Benjamin Fair" <benjaminfair at google.com<mailto:benjaminfair at google.com>> wrote:

    On Mon, 30 Mar 2020 at 13:00, Vijay Khemka <vijaykhemka at fb.com<mailto:vijaykhemka at fb.com>> wrote:
    >
    > Hi Jason,
    >
    > We have a requirement of Chassis sled cycle and it can be achieved by sending an i2c command to hotswap controller. Is there any plan to add this feature in x86-power-control. It should take i2c bus address from configuration file.
    >
    >
    >
    > Regards
    >
    > -Vijay

    This feature is implemented on some systems using an IPMI OEM command:
    https://github.com/openbmc/google-ipmi-sys#delayedhardreset---subcommand-0x03

    It currently just activates the systemd target
    gbmc-psu-hardreset.target and lets you register services to do the
    actual hotswap reset (usually by toggling a GPIO). Having a unified
    solution in x86-power-control for this would be great!

Ben, Can you please share content of
 https://github.com/openbmc/google-ipmi-sys/blob/master/gbmc-psu-hardreset.target
as my assumption is each platform needs to provide this file but I couldn't find any platform
using this. I only found reference in meta-quanta which is deleting this file. So please
provide a reference to this file.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20200401/11e7a033/attachment.htm>


More information about the openbmc mailing list