system power control
Bills, Jason M
jason.m.bills at linux.intel.com
Tue Aug 11 03:33:48 AEST 2020
On 8/7/2020 6:19 PM, Zhao Kun wrote:
> Thank you, Jason. Could you share with me any example of defining those
> GPIOs in device tree for x86-power-control? I can’t find any in
Sorry for not sending link before. You can find our DTS implementation
> Best regards,
> Kun Zhao
> zkxz at hotmail.com <mailto:zkxz at hotmail.com>
> *From: *Bills, Jason M <mailto:jason.m.bills at linux.intel.com>
> *Sent: *Friday, August 7, 2020 10:12 AM
> *To: *openbmc at lists.ozlabs.org <mailto:openbmc at lists.ozlabs.org>
> *Subject: *Re: system power control
> On 8/6/2020 11:43 PM, Zhao Kun wrote:
> > Hi,
> > I’m new to learn how to make OpenBMC work on a X86 based system.
> > Currently I met a problem of mapping the GPIOs about power
> > on/off/reset/status into OpenBMC logic. I understand when user issue a
> > power on request through any user interfaces like RESTful, IPMI, etc.,
> > some service (phosphor-state-manager?) will be triggered to check
> > current status and roll out corresponding systemd services to do the
> > job. (please correct me if I’m wrong)
> > But I’m just confused on how those services actually toggle or check the
> > GPIOs, there seems be many choices,
> > 1. Device tree?
> > 2. Using Workbook gpio_defs.json?
> > 3. Create some services calling platform specific scripts to operate
> > GPIO or I2C devices?
> > 4. Using x86-power-control?
> > So what’s the most recommended way to do it? Really appreciated If
> > anyone can share some lights.
> On Intel reference platforms, we use x86-power-control and configure the
> GPIO names using device tree.
> > I thought there must be a mechanism to consume some kind of
> > configuration file as the hardware abstraction layer. So I guess it
> > might be gpio_defs.json or device tree.
> > Thanks.
> > Best regards,
> > Kun Zhao
> > /*
> > zkxz at hotmail.com <mailto:zkxz at hotmail.com>
> > */
More information about the openbmc