From: Patrick Williams <patrick@stwcx.xyz>
To: "P. Priyatharshan" <PriyatharshanP@hcl.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"ed@tanous.net" <ed@tanous.net>,
"Velumani T-ERS, HCLTech" <velumanit@hcl.com>,
Vijay Khemka <vijaykhemka@fb.com>
Subject: Re: 12v slot AC Support in x86-power-control
Date: Fri, 9 Oct 2020 14:48:46 -0500 [thread overview]
Message-ID: <20201009194846.GN6152@heinlein> (raw)
In-Reply-To: <TY2PR04MB3311209CF7859852B33802E8CA080@TY2PR04MB3311.apcprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
On Fri, Oct 09, 2020 at 03:49:55PM +0000, P. Priyatharshan wrote:
> The earlier "power on/off/cycle the computer card" sequence will only handle the computer card portion of the host.
> But the new feature [Slot on/off/cycle] will power cycles the entire card [ BIC + computer card portion + rest of the hardware in twin lake] for each slot.
Got it now.
Take a look at [1]. You should implement the 'chassisN' objects (in
x86-power-control?) to handle the normal power sequence to each of your
compute cards. I think in your case N = 1:4. You should also implement
the 'chassis_system0' object, which will be a full power cycle of the
entire system. Finally, you'll want to implement 'chassis_systemN'
(again N = 1:4) to do the slot-level full power cycle.
1. https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/xyz/openbmc_project/State#chassis-system
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-10-09 19:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 15:49 12v slot AC Support in x86-power-control P. Priyatharshan
2020-10-09 19:48 ` Patrick Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-11 6:39 P. Priyatharshan
2020-10-06 16:43 P. Priyatharshan
2020-10-07 1:51 ` Patrick Williams
2020-10-08 0:41 ` Vijay Khemka
2020-10-08 13:13 ` P. Priyatharshan
2020-10-08 13:45 ` Anton Kachalov
2020-10-08 14:55 ` P. Priyatharshan
2020-10-08 16:31 ` 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=20201009194846.GN6152@heinlein \
--to=patrick@stwcx.xyz \
--cc=PriyatharshanP@hcl.com \
--cc=ed@tanous.net \
--cc=openbmc@lists.ozlabs.org \
--cc=velumanit@hcl.com \
--cc=vijaykhemka@fb.com \
/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).