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: Tue, 6 Oct 2020 20:51:03 -0500 [thread overview]
Message-ID: <20201007015103.GH6152@heinlein> (raw)
In-Reply-To: <TY2PR04MB3311FEF038529B122E1123DECA0D0@TY2PR04MB3311.apcprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
On Tue, Oct 06, 2020 at 04:43:27PM +0000, P. Priyatharshan wrote:
> Hi Vijay,
>
> I am working on a patch to support 12v slot AC cycle in x86-power-control.This can be enabled by configuring slotACPowerName in json config file.Since you are also working on similar kind of feature in x86-power-control, I would like bring up this discussion on mailing list to understand how these two features, and the design you proposed for chassis reset are intended to work together.Kindly go through my design changes below and share your thoughts.
Can you expand on what a "12v slot AC cycle" means? I can't decipher
it.
Vijay was working on a complete power cycle of the entire server, as if
it were unplugged and plugged back in. This was done as a different
object (chassis_system0) from the object representing the host (chassis0).
The chassis0 typically models the power rails that drive the host
processor. The power cycle of those is already the primary feature of
x86-power-control. Can you expand on what the differences are with the
system you're working on?
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-10-07 1:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 16:43 12v slot AC Support in x86-power-control P. Priyatharshan
2020-10-07 1:51 ` Patrick Williams [this message]
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
2020-10-09 15:49 P. Priyatharshan
2020-10-09 19:48 ` Patrick Williams
2020-10-11 6:39 P. Priyatharshan
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=20201007015103.GH6152@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).