From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH] W83627EHF driver update
Date: Mon, 26 Jun 2006 19:33:10 +0000 [thread overview]
Message-ID: <20060626213310.fdaa81e1.khali@linux-fr.org> (raw)
In-Reply-To: <4485CB7A.9050209@sh.cvut.cz>
Hi Rudolf,
> > I am happy with the code now, but there is a problem with the sysfs file
> > names, see below.
>
> Ok. I'm attaching fixed versions of both.
>
> > And manual fan speed control too.
>
> Ok I will mention, although I considered this a special case
> of automatic regulation
>
> > We should at least have read-only files to let the user know the
> > mapping.
>
> The mapping is trivial and programmable for fan4 only.
> I fixed the docs.
>
> > I'm just realizing that these names are quite wrong. For example
> > temp1_target may not be related to temp1 but to a different temperature
> > sensor depending on the temp/fan mapping. The "1" here really means
> > pwm1, not temp1. So these files should be named pwm[1-4]_target_temp
> > and pwm[1-4]_tolerance_temp, respectively.
>
> Yes correct. Fixed.
Thanks.
> If we consider this as standard for some chips. We would need some mapping
> standard too (Yuan did some file for w83793)
The temp <-> pwm mapping standard already exists.
> > But the driver uncondionally creates both files? This needs to be
> > investigated, and fixed (either the driver or the documentation.)
>
> I fixed the note. The files are used in SF3 iirc, so we might have them.
I'm still not exactly happy. Documenting that we implemented things in
a possibly non-working way is better than not documenting it, agreed,
but even better would be to have things working in the first place.
Also on the to do list is the export of the fan <-> temperature
mapping, at least read only, as I asked before already. For now pwm4 is
useless in Temperature Cruise mode, as you don't know what temperature
channel it is working with.
Anyway, I will apply these patches now, as we have gone trough many
review cycles already. I made some fixes to the documentation patch to
fix typos and reword one sentence. Any future change to the w83627ehf
driver or its documentation should be incremental on top of these
patches.
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2006-06-26 19:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 18:37 [lm-sensors] [PATCH] W83627EHF driver update Rudolf Marek
2006-06-06 21:02 ` David Hubbard
2006-06-07 10:29 ` Jim Cromie
2006-06-07 20:51 ` David Hubbard
2006-06-07 21:00 ` Rudolf Marek
2006-06-07 21:06 ` Rudolf Marek
2006-06-07 22:13 ` Sylvain Jeaugey
2006-06-08 1:01 ` David Hubbard
2006-06-08 7:51 ` Sylvain Jeaugey
2006-06-12 16:30 ` Jean Delvare
2006-06-12 23:12 ` David Hubbard
2006-06-13 8:53 ` Jean Delvare
2006-06-13 16:03 ` David Hubbard
2006-06-14 12:48 ` Rudolf Marek
2006-06-14 15:06 ` Jean Delvare
2006-06-14 15:14 ` Rudolf Marek
2006-06-14 15:50 ` Jean Delvare
2006-06-14 21:29 ` Rudolf Marek
2006-06-15 14:55 ` David Hubbard
2006-06-15 15:20 ` Sylvain Jeaugey
2006-06-16 4:29 ` David Hubbard
2006-06-16 21:33 ` Rudolf Marek
2006-06-19 15:53 ` David Hubbard
2006-06-20 12:41 ` Jean Delvare
2006-06-21 15:10 ` David Hubbard
2006-06-24 16:42 ` Rudolf Marek
2006-06-25 14:04 ` Jean Delvare
2006-06-25 16:00 ` Rudolf Marek
2006-06-26 19:33 ` Jean Delvare [this message]
2006-06-26 20:34 ` Rudolf Marek
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=20060626213310.fdaa81e1.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.