From: hjk@linutronix.de (Hans-Jürgen Koch)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH] Add MAX6650 support
Date: Tue, 27 Feb 2007 19:58:26 +0000 [thread overview]
Message-ID: <200702272058.27507.hjk@linutronix.de> (raw)
In-Reply-To: <200701171359.46334.hjk@linutronix.de>
Am Dienstag, 27. Februar 2007 19:07 schrieb Jean Delvare:
>
> > Do the count, speed and config also have to be modified to follow a
> > convention?
>
> The count and config files are non-standard files so they don't have to
> follow any specific convention. In fact I would even remove these
> files, in particular the config file infringes the fundamental sysfs
> rule. And the count file isn't particularly useful.
Well, the current implementation assumes that the MAX6650 is initialized by
the BIOS. On the other hand, the 5V/12V setting is done by the driver, the
value is hardcoded in the source. This doesn't look like a clean solution.
I suggest to add module parameters to allow configuration of 5V/12V,
prescaler, count and mode. Then we _know_ the settings and can drop the
config and the count file. We also get rid of the hardcoded 5V/12V setting
and don't need to rely on a BIOS that might or might not do what we want.
Any objections?
>
> The speed file, what is it doing? If it is used to set the desired fan
> speed, then the right name would be fan1_target. Does it only apply to
> one fan or all? Is it always active?
It sets the speed of the single fan for a MAX6650. For a MAX6651, it sets a
speed that is valid for all connected fans, if I understand the data sheet
correctly. In any case, this works only if mode is set to "closed loop".
Thanks,
Hans
next prev parent reply other threads:[~2007-02-27 19:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 12:59 [lm-sensors] [PATCH] Add MAX6650 support Hans-Jürgen Koch
2007-01-22 8:36 ` Jean Delvare
2007-02-11 15:44 ` corentin.labbe
2007-02-11 16:22 ` Hans-Jürgen Koch
2007-02-12 13:48 ` Hans-Jürgen Koch
2007-02-27 15:21 ` [lm-sensors] " Matej Kenda
2007-02-27 15:35 ` [lm-sensors] " Jean Delvare
2007-02-27 16:17 ` Hans-Jürgen Koch
2007-02-27 16:29 ` Matej Kenda
2007-02-27 17:03 ` Matej Kenda
2007-02-27 17:13 ` Hans-Jürgen Koch
2007-02-27 18:07 ` Jean Delvare
2007-02-27 19:58 ` Hans-Jürgen Koch [this message]
2007-02-28 11:44 ` Hans-Jürgen Koch
2007-02-28 15:57 ` Matej Kenda
2007-02-28 16:08 ` Hans-Jürgen Koch
2007-03-01 7:15 ` Jean Delvare
2007-03-01 7:34 ` Jean Delvare
2007-03-01 10:11 ` Hans-Jürgen Koch
2007-03-01 17:34 ` corentin.labbe
2007-03-02 11:32 ` Jean Delvare
2007-03-05 11:34 ` Hans-Jürgen Koch
2007-03-11 14:40 ` Jean Delvare
2007-03-11 15:21 ` Jean Delvare
2007-03-11 21:08 ` Hans-Jürgen Koch
2007-03-12 13:50 ` Jean Delvare
2007-03-12 14:44 ` Hans-Jürgen Koch
2007-03-12 16:49 ` Jean Delvare
2007-03-13 13:25 ` Hans-Jürgen Koch
2007-03-15 20:10 ` Jean Delvare
2007-03-16 16:44 ` Hans-Jürgen Koch
2007-03-16 19:17 ` Jean Delvare
2007-03-16 21:07 ` Hans-Jürgen Koch
2007-03-16 21:19 ` Hans-Jürgen Koch
2007-03-16 21:19 ` Thomas Gleixner
2007-03-16 21:33 ` Thomas Gleixner
2007-03-17 13:39 ` Jean Delvare
2007-03-17 14:23 ` Hans-Jürgen Koch
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=200702272058.27507.hjk@linutronix.de \
--to=hjk@linutronix.de \
--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.