openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Thang Nguyen <thang@amperemail.onmicrosoft.com>
To: openbmc@lists.ozlabs.org
Subject: Re: Implement OEM mechanism to handle xyz.openbmc_project.Condition.HostFirmware interface
Date: Thu, 9 Sep 2021 08:54:59 +0700	[thread overview]
Message-ID: <3909e9e3-0a58-e542-a004-89278438997d@amperemail.onmicrosoft.com> (raw)
In-Reply-To: <53e204da-0c8b-d161-a065-a6195550d7f7@amperemail.onmicrosoft.com>

Hi,

Let me explain more detail about our cases:

- Our system uses a GPIO called FW_BOOT_OK to detect if the Host is 
currently ON or OFF. The Host firmware set this GPIO when the first core 
initialized.

- We have no problem in Host State with power control. But the problem 
is in the case of BMC rebooted while the Host is ON.

- Before the commit 
https://github.com/openbmc/phosphor-state-manager/commit/0d1c3f1f9329c853677f0581287afef83eeea0f0, 
phosphor-reset-host-check@.service  is used to check and update Host 
State in case of BMC rebooted. But after that commit, the service file 
was removed. This makes no target service to update the Host State and 
the host check is fail at 
https://github.com/openbmc/phosphor-state-manager/blob/0a675215d6a6d2eb13e030ba0f618a4691de58d4/host_check.cpp#L109.

We would like to ask for your idea on how should we implement for the 
Host check when BMC is rebooted?


Thanks,

Thang Q. Nguyen

On 08/09/2021 20:19, Thu Nguyen wrote:
> Dear Geissonator,
>
>
> After commit 
> https://github.com/openbmc/phosphor-state-manager/commit/0d1c3f1f9329c853677f0581287afef83eeea0f0
>
> when BMC boots up, phosphor-host-state directly checks  the host state 
> thru interface xyz.openbmc_project.Condition.HostFirmware.
>
> It does not check the existing of /run/openbmc/host@%d-on as before.
>
>
> I plan to implement "oem mechanism" to handle the interface 
> xyz.openbmc_project.Condition.HostFirmware.
>
> Which will use the GPIO interface to update the host state. I 
> researched the code handle this interface in phosphor-host-ipmi and pldm.
>
> I wonder which repo should I upstream the code? Currently, we don't 
> have any OEM repo in github to upstream the code.
>
> Do you have any idea to handle interface in bash scripts?
>
>
> Regards.
>
> Thu Nguyen.
>
>
>
>
>
>
>

  reply	other threads:[~2021-09-09  1:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08 13:19 Thu Nguyen
2021-09-09  1:54 ` Thang Nguyen [this message]
2021-09-09 15:42   ` Andrew Geissler
2021-09-10 11:34     ` Thu Nguyen
2021-09-10 21:57       ` Andrew Geissler
2021-09-11  3:07         ` Thu Nguyen
2021-09-14 21:16           ` Andrew Geissler

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=3909e9e3-0a58-e542-a004-89278438997d@amperemail.onmicrosoft.com \
    --to=thang@amperemail.onmicrosoft.com \
    --cc=openbmc@lists.ozlabs.org \
    --subject='Re: Implement OEM mechanism to handle xyz.openbmc_project.Condition.HostFirmware interface' \
    /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

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).