All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark van Doesburg <mark.vandoesburg@hetnet.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH 2.6.25.4] f71882.c driver,
Date: Wed, 11 Jun 2008 19:41:29 +0000	[thread overview]
Message-ID: <200806111941.m5BJfTpl003204@localhost> (raw)
In-Reply-To: <200806110520.m5B5KDgO018954@localhost>

Hello Hans,

Your proposal sounds fine to me. I wasn't too happy with the fan?_target
pwm? conflict either.  So I will implement the following:

	1. Remove fan?_target.
	2. Add fan?_full_speed.
	3. Interpret pwm? as the duty cycle when in duty cycle mode.
	4. Scale pwm? from 0..255 to 0..fan?_full_speed when in rpm mode.
	5. Change the behavior of pwm?_enable not to change pwm vs. duty
	   cycle mode.
	5. Add module option to select rpm/duty cycle mode.  
	6. Add pwm?_auto*

This will take some time of course. (Although being able to read the
temperature of my "Asus EAH3650 silent" would speed things up ;-)

My BIOS doesn't put a usefull value in the full speed register. There is
also no way to set the case fan to anything but a fixed PWM value. Then
again I build the computer from seperate components, I can imagine a
fully assembled system could do more.

regards,

Mark van Doesburg.


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2008-06-11 19:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11  5:20 [lm-sensors] [PATCH 2.6.25.4] f71882.c driver, Mark van Doesburg
2008-06-11  8:18 ` Goede, J.W.R. de
2008-06-11 19:41 ` Mark van Doesburg [this message]
2008-06-12  8:05 ` Hans de Goede
2008-06-25  6:14 ` Mark van Doesburg
2008-06-25  7:22 ` Hans de Goede
2008-06-30 19:23 ` Mark van Doesburg
2008-06-30 21:02 ` Mark van Doesburg
2008-08-04 14:05 ` Hans de Goede
2008-10-07 18:36 ` Mark van Doesburg
2008-10-10 22:57 ` Andrew Morton

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=200806111941.m5BJfTpl003204@localhost \
    --to=mark.vandoesburg@hetnet.nl \
    --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.