Hi, Priyatharshan This feature sound like adding more chassisX objects. Do you have separate sensors (e.g. on i2c bus or busses) per each board in the slots? On Thu, Oct 8, 2020, 15:15 P. Priyatharshan wrote: > Thanks Vijay/Patrick for your comments. > > The feature we are working is different from vijay's feature. > > Out platform is multi host system and we have the host as FRU and it can > be plugged in to a slot. The slot has an option to control slot power and > this can be used for a AC cycle. > > We proposed a design to add the slot power control in the > x86-power-control.The earlier discussion can be found in the below link. > > https://lists.ozlabs.org/pipermail/openbmc/2020-August/022481.html > > ed tanous, > > I will create a clear document on when to use this slot power control > feature. > > Thanks, > Priyatharshan P > > ------------------------------ > *From:* Vijay Khemka > *Sent:* 08 October 2020 06:11 > *To:* P. Priyatharshan ; openbmc@lists.ozlabs.org > ; ed@tanous.net > *Cc:* Velumani T-ERS,HCLTech > *Subject:* Re: 12v slot AC Support in x86-power-control > > > [CAUTION: This Email is from outside the Organization. Unless you trust > the sender, Don’t click links or open attachments as it may be a Phishing > email, which can steal your Information and compromise your Computer.] > > Hi Priyatharshan, > > Chassis system reset is for removing AC power for the whole chassis and it > is already supported in x86-power-control. I am working on enabling this > feature in redfish. I am not sure how it is related to your new features. > If it is related then you can also define system_reset target unit. > > > > Regards > > -Vijay > > > > *From: *"P. Priyatharshan" > *Date: *Tuesday, October 6, 2020 at 9:43 AM > *To: *"openbmc@lists.ozlabs.org" , Vijay Khemka > , "ed@tanous.net" > *Cc: *"Velumani T-ERS,HCLTech" > *Subject: *12v slot AC Support in x86-power-control > > > > 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. > > > > I have modified the existing /xyz/openbmc_project/state/chassis0 object to > implement 12V On, Off, and Power Cycle for system which has 12V Slot power > support. > > > > > > If slotACPowerName is disabled and if, > > > > RequestedPowerTransition = > "xyz.openbmc_project.State.Chassis.Transition.Off" then poweroff [existing > functionality not changed] > > > > RequestedPowerTransition = > "xyz.openbmc_project.State.Chassis.Transition.On" then powerOn [existing > functionality not changed] > > > > RequestedPowerTransition = > "xyz.openbmc_project.State.Chassis.Transition.PowerCycle" then PowerCycle > [existing functionality not changed] > > > > events will be called. > > > > > > > > If slotACPowerName is enabled and if, > > > > RequestedPowerTransition = > "xyz.openbmc_project.State.Chassis.Transition.Off" then 12V Ac Slot Off > > > > RequestedPowerTransition = > "xyz.openbmc_project.State.Chassis.Transition.On" then 12V Ac Slot On > > > > RequestedPowerTransition = > "xyz.openbmc_project.State.Chassis.Transition.PowerCycle" then 12V Ac Slot > PowerCycle > > > > events will be called. > > > > Thanks, > > Priyatharshan P > > ::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. > ------------------------------ >