From: mds@paradyne.com (Mark D. Studebaker )
To: lm-sensors@vger.kernel.org
Subject: LM83 driver
Date: Thu, 19 May 2005 06:24:06 +0000 [thread overview]
Message-ID: <3F19E97F.6030705@paradyne.com> (raw)
In-Reply-To: <20030703194558.60bc8955.khali@linux-fr.org>
Of course with libsensors apps you don't care about /proc standards.
The benefit is in writing simple non-libsensors scripts, etc.
(see our new prog/pwm/pwmconfig) which are only feasible if we follow
consistent standards for /proc.
Jean Delvare wrote:
>>For no longer than the /proc standard is going to last (sysfs anyone)
>>I think it would be much better to have a "dummy" value.
>
>
> Why that? Our structures are flexible enough to support that, libsensors
> supports it, sensors supports it. In which case would the dummy value
> help? I just can't see any.
>
> As for the procfs vs. sysfs thing, it is unrelated IMHO. If we are to
> allow 2-values temperature files for sysfs, we can as well do so for
> procfs. If anything needs to be changed to support this (I still don't
> see what yet), it will have to for at least sysfs so it maybe won't even
> notice it's the same for some recent procfs drivers.
>
> Of course, adding a dummy value is easy and we already have at least one
> driver that does it - adm1021 for lm84 - but I don't like adding
> constraints when I feel they will only slow us down on our path to
> progress. Letting the driver choose how many temperature values it wants
> to repport is a good idea, methinks. One could imagine drivers only
> repporting the current value, or max and current (this is the case for
> my lm83 driver), or over, hyst and current as most of our drivers do.
> But there are other possibilities, such as max, min, current (I think we
> have some drivers that do that) or max, hystmax, min, hystmin and
> current resulting in a 5-value file. The same could apply to other
> measures such as in's and fan's.
>
> The fact that we try to have a common base for all sensor drivers
> doesn't mean we must ignore chips specificity. Sadly, it looks like this
> is what we tend to do when a single drivers support many, many chips. I
> think that's something we should think about. After all, that's the idea
> Unix is living with for decades (do one thing and do it well).
>
> Comments welcome, of course.
>
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 LM83 driver Jean Delvare
2005-05-19 6:24 ` Greg KH
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Greg KH
2005-05-19 6:24 ` Greg KH
2005-05-19 6:24 ` Philip Pokorny
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Mark D. Studebaker [this message]
2005-05-19 6:24 ` ZOleg Matrix
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=3F19E97F.6030705@paradyne.com \
--to=mds@paradyne.com \
--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.