All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Tanous <ed@tanous.net>
To: Kumar Thangavel <thangavel.k@hcl.com>
Cc: Zhikui Ren <zhikui.ren@intel.com>,
	Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>,
	Patrick Venture <venture@google.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
	Vernon Mauery <vernon.mauery@linux.intel.com>,
	"Velumani T-ERS, HCLTech" <velumanit@hcl.com>,
	Patrick Williams <patrickw3@fb.com>
Subject: Re: Fault handling(Threshold exceeds/low) in Fan and NIC sensors
Date: Mon, 16 Nov 2020 07:59:02 -0800	[thread overview]
Message-ID: <CACWQX82oZiC0e6DJd=M10COJOqORy-ZJyB5biXyecFw26zpaLg@mail.gmail.com> (raw)
In-Reply-To: <HK0PR04MB2964EA39F0F9AD7ED1A03535FDE30@HK0PR04MB2964.apcprd04.prod.outlook.com>

On Mon, Nov 16, 2020 at 5:05 AM Kumar Thangavel <thangavel.k@hcl.com> wrote:
>
> Classification: Internal
>
> Hi Ed,
>
>         In short, Our requirement is to take the actions when the fan fails. That action is platform specific.
>
>         Fan failure :  This is based on Fan sensors. If fan sensor's tach values is less than 33%, will consider as a fan failure. So will take the actions to reduce the heat production in the system.

dbus-sensors and phosphor-pid-control already have mechanisms for
handling fan failure in these ways.  Take a look at the existing
config files, and they'll guide you on what you need to do next.

>                                 So that,  hosts, NIC and other power consuming modules.
>
>         Dbus-sensor's already handles the threshold masking. We just use that threshold masking to take the platform specific actions.
>
>         Please let us know if any clarifications needed.
>
> Thanks,
> Kumar.

Ps, Please don't toppost.

  reply	other threads:[~2020-11-16 16:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 16:30 Fault handling(Threshold exceeds/low) in Fan and NIC sensors Kumar Thangavel
2020-11-13 20:44 ` Ed Tanous
2020-11-16 13:05   ` Kumar Thangavel
2020-11-16 15:59     ` Ed Tanous [this message]
2020-11-17 11:59       ` Kumar Thangavel
2020-11-20 17:10         ` 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='CACWQX82oZiC0e6DJd=M10COJOqORy-ZJyB5biXyecFw26zpaLg@mail.gmail.com' \
    --to=ed@tanous.net \
    --cc=jae.hyun.yoo@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=patrickw3@fb.com \
    --cc=thangavel.k@hcl.com \
    --cc=velumanit@hcl.com \
    --cc=venture@google.com \
    --cc=vernon.mauery@linux.intel.com \
    --cc=zhikui.ren@intel.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.