From: Matthew Barth <msbarth@linux.ibm.com>
To: Andrei Kartashev <a.kartashev@yadro.com>,
Thu Nguyen OS <thu@os.amperecomputing.com>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Add phosphor-fan configuration for the fan which added by dbus-sensor
Date: Thu, 6 May 2021 08:13:44 -0500 [thread overview]
Message-ID: <3ab7f192-0830-56cf-583e-7fffd41a50a9@linux.ibm.com> (raw)
In-Reply-To: <f5eedf23bfea01b5d69b43f4d35970f45f5d4e99.camel@yadro.com>
On 5/6/21 4:40 AM, Andrei Kartashev wrote:
> Hello,
>
> I guess, when using dbus-sensors, you supposed to use phosphor-pid-
> control package to control fans.
Could you explain this statement further? These apps should be using the same fan sensor dbus interfaces to control fans, so there should be no reason the use of these apps together are required to control fans.
>
> On Thu, 2021-05-06 at 09:22 +0000, Thu Nguyen OS wrote:
>> Hi,
>>
>> I’m supporting the fan control algorithms using phosphor-fan.
>> Phosphor-fan monitoring and controlling require interface
>> xyz.openbmc_project.Control.FanPwm in the fan inventory object.
>> https://github.com/openbmc/phosphor-fan-presence/blob/master/docs/monitor/inventory.md
>>
>> But FanSensor daemon of dbus-sensor only adds
>> /xyz/openbmc_project/sensors/fan_tach to inventory list, and this
>> path don’t support xyz.openbmc_project.Control.FanPwm interface.
>>
>> Do you have any solution to make phosphor-fan work with dbus-sensor?
>>
>> I’m currently update FanSensor in dbus-sensor to add
>> xyz.openbmc_project.Control.FanPwm to
>> /xyz/openbmc_project/sensors/fan_tach.
>>
>> Regards.
>> Thu Nguyen.
next prev parent reply other threads:[~2021-05-06 13:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 9:22 Add phosphor-fan configuration for the fan which added by dbus-sensor Thu Nguyen OS
2021-05-06 9:40 ` Andrei Kartashev
2021-05-06 13:13 ` Matthew Barth [this message]
2021-05-06 13:08 ` Matthew Barth
2021-05-06 15:59 ` Thu Nguyen OS
2021-05-06 16:30 ` Matthew Barth
2021-05-06 22:34 ` Thu Nguyen OS
2021-05-07 16:22 ` Matthew Barth
2021-05-08 16:41 ` Thu Nguyen
2021-05-10 18:14 ` Matthew Barth
2021-05-11 14:11 ` Thu Nguyen
2021-05-11 18:25 ` Matthew Barth
2022-07-05 23:16 Maheswara Kurapati (QUIC)
2022-07-08 20:27 ` Matt Spinler
2022-07-08 20:33 ` Maheswara Kurapati
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=3ab7f192-0830-56cf-583e-7fffd41a50a9@linux.ibm.com \
--to=msbarth@linux.ibm.com \
--cc=a.kartashev@yadro.com \
--cc=openbmc@lists.ozlabs.org \
--cc=thu@os.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.