From: Matt Spinler <mspinler@linux.ibm.com>
To: Thu Ba Nguyen <tbnguyen1985@gmail.com>, openbmc@lists.ozlabs.org
Subject: Re: Enable/Disable some sensors when Host On/Off
Date: Mon, 19 Oct 2020 09:16:03 -0500 [thread overview]
Message-ID: <4ff7b0cc-8e61-7fa7-19be-8427f281a0fc@linux.ibm.com> (raw)
In-Reply-To: <CALioo35zJdqL7uAhvxAuqa7c16wAdtfc+JVSz6Tg5UG5Yp8L3w@mail.gmail.com>
On 10/18/2020 8:58 AM, Thu Ba Nguyen wrote:
> Dear, I'm supporting the host sensors for Ampere Computing LLC
> platform. We are...
> This Message Is From an External Sender
> This message came from outside your organization.
>
> Dear,
>
> I'm supporting the host sensors for Ampere Computing LLC platform.
> We are using phosphor-hwmon to update values of sensors and monitoring
> sensors warning/errors base on threshold setting.
>
> There are some sensors which are turned off when host Off. It can be
> the sensors reported by host or voltage/temperature/power sensors
> which use the same power source with host.
>
> I researched in openBmc sensor-architecture documents but can't find
> any option to enable/disable sensors base on one status or GPIO pins.
> I can't use REMOVERCS.
>
> Research in phosphor-hwmon code, I don't see the answer too.
>
> Do we have any options/solution to Enable/Disable some sensors when
> Host On/Off?
Hi,
The phosphor-hwmon code doesn't support that yet. It has been discussed
before but nobody
has implemented it.
>
> Thanks.
> Thu Nguyen.
next prev parent reply other threads:[~2020-10-19 14:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 13:58 Enable/Disable some sensors when Host On/Off Thu Ba Nguyen
2020-10-19 14:16 ` Matt Spinler [this message]
2020-10-19 15:23 ` Thu Ba Nguyen
2020-10-20 13:46 ` Matt Spinler
2020-10-20 14:18 ` Patrick Williams
2020-10-20 21:26 ` Matt Spinler
2020-10-20 23:21 ` Thu Ba Nguyen
2020-10-20 23:39 ` Thu Ba Nguyen
2020-10-20 23:16 ` Thu Ba Nguyen
2020-10-19 17:31 ` Ed Tanous
2020-10-19 18:22 ` Thu Ba Nguyen
2020-10-19 18:31 ` Ed Tanous
2020-10-20 23:05 ` Thu Ba Nguyen
2020-10-21 0:15 ` Vijay Khemka
2020-10-21 16:54 ` Thu Ba Nguyen
2020-10-22 14:49 ` Thu Ba Nguyen
2020-10-22 15:51 ` Matt Spinler
2020-10-22 22:45 ` Thu Ba Nguyen
2020-11-04 9:15 ` Thu Ba Nguyen
2020-11-04 16:31 ` Matt Spinler
2020-11-04 22:18 ` Thu Ba Nguyen
2020-11-05 20:52 ` Matt Spinler
2020-11-05 23:16 ` Thu Ba Nguyen
2020-11-05 23:24 ` Matt Spinler
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=4ff7b0cc-8e61-7fa7-19be-8427f281a0fc@linux.ibm.com \
--to=mspinler@linux.ibm.com \
--cc=openbmc@lists.ozlabs.org \
--cc=tbnguyen1985@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).