openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "P. Priyatharshan" <PriyatharshanP@hcl.com>
To: Patrick Williams <patrick@stwcx.xyz>
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: Sun, 11 Oct 2020 06:39:06 +0000	[thread overview]
Message-ID: <TY2PR04MB3311E950C08F4CA31789A275CA060@TY2PR04MB3311.apcprd04.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2591 bytes --]

Hi Patrick,

Thanks for the clarification.Got things cleared now.

As you mentioned, I will implement chassis_system0 object for full power cycle of the
entire system, and 'chassis_systemN' [N = 1:4 for my case] to do the slot-level full power cycle in x86-power-control.

Thanks,
Priyatharshan P

________________________________
From: Patrick Williams
Sent: Saturday, October 10, 2020 01:18
To: P. Priyatharshan
Cc: Vijay Khemka; openbmc@lists.ozlabs.org; ed@tanous.net; Velumani T-ERS,HCLTech
Subject: Re: 12v slot AC Support in x86-power-control

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
::DISCLAIMER::
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
________________________________

[-- Attachment #2: Type: text/html, Size: 4659 bytes --]

             reply	other threads:[~2020-10-11  6:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-11  6:39 P. Priyatharshan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-10-09 15:49 12v slot AC Support in x86-power-control P. Priyatharshan
2020-10-09 19:48 ` Patrick Williams
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=TY2PR04MB3311E950C08F4CA31789A275CA060@TY2PR04MB3311.apcprd04.prod.outlook.com \
    --to=priyatharshanp@hcl.com \
    --cc=ed@tanous.net \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrick@stwcx.xyz \
    --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).