From: Brandon Wyman <bjwyman@gmail.com>
To: Chanh Nguyen OS <chanh@os.amperecomputing.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: "spinler@us.ibm.com" <spinler@us.ibm.com>,
Thang Nguyen <thangqn@amperecomputing.com>,
"shawnmm@us.ibm.com" <shawnmm@us.ibm.com>,
Phong Vo <pvo@amperecomputing.com>
Subject: Re: [Phosphor-power] psu-ng: Add method to get PSU conf from D-Bus.
Date: Thu, 24 Jun 2021 12:50:02 -0500 [thread overview]
Message-ID: <7a434ef2-c15d-be17-e443-2eedf5fc3ed4@gmail.com> (raw)
In-Reply-To: <SN6PR01MB4973940AAE8F62B61613C2BB95089@SN6PR01MB4973.prod.exchangelabs.com>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
On 2021-06-23 04:11, Chanh Nguyen OS wrote:
> Hi B. J. Wyman,
>
> I'm using the psu-ng to monitor the PSU. I used the
> */pmbus/*(https://github.com/openbmc/linux/blob/dev-5.10/Documentation/hwmon/pmbus.rst
> <https://github.com/openbmc/linux/blob/dev-5.10/Documentation/hwmon/pmbus.rst>)
> driver to support hardware monitoring for the PSU, don't use the
> */ibm-cffps/*driver
> (https://github.com/openbmc/linux/blob/dev-5.10/Documentation/hwmon/ibm-cffps.rst
> <https://github.com/openbmc/linux/blob/dev-5.10/Documentation/hwmon/ibm-cffps.rst>)
>
> I don't clear why we fix to use the *IBMCFFPSInterface
> (https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-power/+/38138/10/phosphor-power-supply/psu_manager.cpp#16
> <https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-power/+/38138/10/phosphor-power-supply/psu_manager.cpp#16>)* ?
Yeah, that was sort of a short-sighted updated. That probably should
have been something configurable:
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-power/+/43018/8/phosphor-power-supply/power_supply.cpp#30
That is used to get the power supply information off of D-Bus, hopefully
populated by the entity-manager service.
https://github.com/openbmc/entity-manager/blob/master/schemas/IBM.json
https://github.com/openbmc/entity-manager/blob/master/configurations/Nisqually.json
This should *NOT* be IBM specific, but I had some kind of blinders on
when I wrote this.
>
> Thanks,
> Chanh Nguyen
>
[-- Attachment #2: Type: text/html, Size: 5668 bytes --]
prev parent reply other threads:[~2021-06-24 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 9:11 [Phosphor-power] psu-ng: Add method to get PSU conf from D-Bus Chanh Nguyen OS
2021-06-24 17:50 ` Brandon Wyman [this message]
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=7a434ef2-c15d-be17-e443-2eedf5fc3ed4@gmail.com \
--to=bjwyman@gmail.com \
--cc=chanh@os.amperecomputing.com \
--cc=openbmc@lists.ozlabs.org \
--cc=pvo@amperecomputing.com \
--cc=shawnmm@us.ibm.com \
--cc=spinler@us.ibm.com \
--cc=thangqn@amperecomputing.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.