x86 power control for multi host
Vijay Khemka
vijaykhemka at fb.com
Sat Jan 25 05:33:59 AEDT 2020
On 1/24/20, 9:24 AM, "James Feist" <james.feist at linux.intel.com> wrote:
On 1/23/20 1:37 PM, Vijay Khemka wrote:
> Thanks Jason for quick response.
> Now my another question is can I get this configuration from entity manager for gpio lines or should I have a separate config.json file?
Using EM in this context would allow a single image to support both a
multi-host system and single host system. If that's possible I'd think
that would be better. I guess the question becomes if you have some way
to dynamically detect a multi-host system, that'd be better. If that's
not possible, then you might be stuck with a hardcoded file.
James,
I agree that it would be great to detect multi host dynamically. But we still need to know different GPIO line name or number for each host to monitor. That's why we need this GPIO configuration. It is going to be runtime as user just need to change entries in EM json config. We may enhance this later on.
>
> On 1/23/20, 10:48 AM, "openbmc on behalf of Bills, Jason M" <openbmc-bounces+vijaykhemka=fb.com at lists.ozlabs.org on behalf of jason.m.bills at linux.intel.com> wrote:
>
> On 1/21/2020 3:26 PM, Vijay Khemka wrote:
> > Sorry, missed to add mailing list.
> >
> > *From: *Vijay Khemka <vijaykhemka at fb.com>
> > *Date: *Tuesday, January 21, 2020 at 2:51 PM
> > *To: *James Feist <james.feist at linux.intel.com>,
> > "jason.m.bills at linux.intel.com" <jason.m.bills at linux.intel.com>
> > *Subject: *x86 power control for multi host
> >
> > Hi James/Jason,
> >
> > I am planning to modify x86 power control for multiple host support. As
> > it has hardcoded name host0 but we want to support for multiple number
> > of hosts based on configuration. I am thinking of reading different GPIO
> > lines for each host from a config.json file and then monitor different
> > gpios. Please suggest that if these configuration, I should read from
> > entity-manager >
> > Also looking forward to your thought of this feature addition in
> > existing daemon or should I have separate repo itself?
> If it's configurable, then I don't see any reason not to have it in the
> existing repo. Is it okay to start there and see how big the impact is
> before deciding on a separate repo?
>
> >
> > Regards
> >
> > -Vijay
> >
>
>
More information about the openbmc
mailing list