Re: Implement OEM mechanism to handle xyz.openbmc_project.Condition.HostFirmware interface

[Thang Nguyen <thang@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.
>
>
>
>
>
>
>