From: davidsen@tmr.com (Bill Davidsen)
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: [PATCH] I2C update for 2.6.9
Date: Thu, 19 May 2005 06:25:20 +0000 [thread overview]
Message-ID: <417D4621.5010604@tmr.com> (raw)
In-Reply-To: <10982315063481@kroah.com>
Greg KH wrote:
> Trip points
> =====>
> Trip points are now numbered (point1, point2, etc...) instead of named
> (_off, _min, _max, _full...). This solves the problem of various chips
> having a different number of trip points. The interface is still chip
> independent in that it doesn't require chip-specific knowledge to be
> used by user-space apps.
It would seem that all chips would have off, max, full, etc, but mapping
nondescript names into functionality may require some chip info anyway.
As you note, with some chips these are not nice linear points on a line,
so it would seem to tell if the top points were "max norm" and "max
safe" vs. "critical" and "shutdown NOW" is still going to need some
information on the chip, both points and operating range.
That's an observation, not a complaint, not even a question unless you
feel the urge to enlighten me.
>
> The reason for this change is that newer chips tend to have more trip
> points. the LM63 has 8, the LM93 has no less than 12. Also, I read in
> the LM63 datasheet that ideal pwm vs temperature curve were parabolic in
> shape. Seems hard to achieve this if we arbitrarily lock the number of
> trip points to 3 ;)
>
> I also introduced an optional hysteresis temperature for trip points.
> The LM63 has this. Since it makes full sense I'd expect other chips to
> propose this as well.
>
> As before, there are two sets of files, each chip driver picks the one
> matching its internal model: trip points are either temperature
> channel-dependent (ADM1031...) or pwm channel-dependent (IT87xx...). If
> we ever come accross fan speed-driven pwm outputs where trip points are
> fan channel-dependent we may have to offer a third set of files. We'll
> see when/if this happens.
>
> I hope I have taken everyone's comments and advice into account and we
> can make this interface proposal part of the sysfs interface standard
> now. I'm sorry it took so long. Comments welcome.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
WARNING: multiple messages have this Message-ID (diff)
From: Bill Davidsen <davidsen@tmr.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: Re: [PATCH] I2C update for 2.6.9
Date: Mon, 25 Oct 2004 14:29:53 -0400 [thread overview]
Message-ID: <417D4621.5010604@tmr.com> (raw)
In-Reply-To: <10982315063481@kroah.com>
Greg KH wrote:
> Trip points
> ===========
>
> Trip points are now numbered (point1, point2, etc...) instead of named
> (_off, _min, _max, _full...). This solves the problem of various chips
> having a different number of trip points. The interface is still chip
> independent in that it doesn't require chip-specific knowledge to be
> used by user-space apps.
It would seem that all chips would have off, max, full, etc, but mapping
nondescript names into functionality may require some chip info anyway.
As you note, with some chips these are not nice linear points on a line,
so it would seem to tell if the top points were "max norm" and "max
safe" vs. "critical" and "shutdown NOW" is still going to need some
information on the chip, both points and operating range.
That's an observation, not a complaint, not even a question unless you
feel the urge to enlighten me.
>
> The reason for this change is that newer chips tend to have more trip
> points. the LM63 has 8, the LM93 has no less than 12. Also, I read in
> the LM63 datasheet that ideal pwm vs temperature curve were parabolic in
> shape. Seems hard to achieve this if we arbitrarily lock the number of
> trip points to 3 ;)
>
> I also introduced an optional hysteresis temperature for trip points.
> The LM63 has this. Since it makes full sense I'd expect other chips to
> propose this as well.
>
> As before, there are two sets of files, each chip driver picks the one
> matching its internal model: trip points are either temperature
> channel-dependent (ADM1031...) or pwm channel-dependent (IT87xx...). If
> we ever come accross fan speed-driven pwm outputs where trip points are
> fan channel-dependent we may have to offer a third set of files. We'll
> see when/if this happens.
>
> I hope I have taken everyone's comments and advice into account and we
> can make this interface proposal part of the sysfs interface standard
> now. I'm sorry it took so long. Comments welcome.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2005-05-19 6:25 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 0:16 [BK PATCH] I2C update for 2.6.9 Greg KH
2005-05-19 6:25 ` Greg KH
2004-10-20 0:18 ` [PATCH] " Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 0:18 ` Greg KH
2004-10-20 5:21 ` Eugene Surovegin
2005-05-19 6:25 ` Eugene Surovegin
2004-10-20 6:26 ` [PATCH] fix recently introduced race in IBM PPC4xx I2C driver Eugene Surovegin
2005-05-19 6:25 ` Eugene Surovegin
2004-10-22 19:55 ` Greg KH
2005-05-19 6:25 ` Greg KH
2004-10-25 18:29 ` Bill Davidsen [this message]
2005-05-19 6:25 ` [PATCH] I2C update for 2.6.9 Bill Davidsen
2004-10-25 20:54 ` Jean Delvare
2005-05-19 6:25 ` Jean Delvare
2004-10-26 21:03 ` Bill Davidsen
2005-05-19 6:25 ` Bill Davidsen
2004-10-20 15:57 ` [BK PATCH] " Jean Delvare
2005-05-19 6:25 ` Jean Delvare
2004-10-20 16:40 ` Lee Revell
2005-05-19 6:25 ` Lee Revell
2004-10-22 21:34 ` Jean Delvare
2005-05-19 6:25 ` Jean Delvare
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=417D4621.5010604@tmr.com \
--to=davidsen@tmr.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sensors@stimpy.netroedge.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.