x86-power-control

[Michael Richardson]

Vijay Khemka <vijaykhemka at fb.com> wrote:
    > 1.  Name of GPIO line, this should be configurable and should also
    > support GPIO number if user doesn’t want to define line name in DTS.

Why in a target system wouldn't naming it in DTS be the most reliable and
most easily accessible mechanism?  I can see that in development being able to define
things helps, but it is not like the production systems would have wire-wrap
where the GPIO pin might change.

    > 2.  All delay time as it varies for us per platform like
    > powerPulseTimeMs is 1 sec instead of 200 ms and powerPulseTimeMs is 6
    > sec instead of 15 sec and these varies for different FB platforms.

    > 3.  GPIO lines to be monitored, not everyone needs SIO_S5 monitoring or NMI_OUT etc.
    > 4.  Enable/disable passthrough

    > Please suggest what is the best way to make these changes. I am ready
    > to work on this to make required change. We can have these config
    > option defined in entity manager or we can accept a new json file for
    > this configuration.

I take it that this isn't a configuration that should be visible to
operators, just to integrators.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr at sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20191017/b7dfabca/attachment.sig>