All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] sysfs interface for fan present capability
Date: Sun, 04 Jun 2006 17:56:21 +0000	[thread overview]
Message-ID: <20060604195621.b5ae7692.khali@linux-fr.org> (raw)
In-Reply-To: <4482843D.5020506@hhs.nl>

> On Sun, 04 Jun 2006, Hans de Goede wrote:
> > I think they are just seeing if it gives any "ticks" at all, so it won't
> > detect a 2 wire fan even if connected to one if its headers.
> 
> Two-wire fans can be detected just as well as three-wire ones, if you
> measure current draw :)  In fact, some chips (like the lm75) can actually
> COUNT ticks on two-wire fans by measuring spikes in the current draw...

Definitely not the LM75, as it is a temperature-only sensor chip. But I
remember reading datasheets mentioning tick count on 2-wires fans,
indeed. Strangely enough, some vendors are doing the opposite and
propose 4-wire fans, the idea being that tick counts tend to be lost
when fan speed control is in use on 3-wire fans.

> If you detect fan presence using ticks, you will never detect a stuck fan on
> startup, which is *dangerous* as it could cause the software inhibit an
> alarm on that fan.

Indeed - which is why I don't want us to emulate it in software.

-- 
Jean Delvare


  parent reply	other threads:[~2006-06-04 17:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-04  6:57 [lm-sensors] sysfs interface for fan present capability Hans de Goede
2006-06-04 15:27 ` Jean Delvare
2006-06-04 17:18 ` Henrique de Moraes Holschuh
2006-06-04 17:20 ` Hans de Goede
2006-06-04 17:42 ` Henrique de Moraes Holschuh
2006-06-04 17:52 ` Jean Delvare
2006-06-04 17:56 ` Jean Delvare [this message]
2006-06-04 17:58 ` Henrique de Moraes Holschuh
2006-06-04 18:09 ` Henrique de Moraes Holschuh
2006-06-04 18:35 ` Jean Delvare
2006-06-04 18:38 ` Jean Delvare
2006-06-04 18:52 ` Henrique de Moraes Holschuh
2006-06-04 19:22 ` Philip Pokorny

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=20060604195621.b5ae7692.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@vger.kernel.org \
    /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.