From: r.marek@sh.cvut.cz (Rudolf Marek)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH] Add fan control support to W83627EHF
Date: Sun, 05 Mar 2006 09:52:18 +0000 [thread overview]
Message-ID: <440AB4D2.4020806@sh.cvut.cz> (raw)
In-Reply-To: <4409FFA1.7050109@sh.cvut.cz>
David Hubbard wrote:
> Hi Rudolf,
> I disagree. If users want to ignore the RPM cruise or speed cruise
> then it's easy to modify the sensors.conf to suit their taste. I agree
> that there isn't a standardized sysfs file for the target RPM, but I
> am planning on using the RPM cruise feature. Yuan has already
> implemented it. I don't think it'd be a problem to support it. Since
> it is present on all four PWM outputs, and Smart Fan 3 isn't, I
> thought it would make sense to have PWM cruise be mode 3.
>
Well it could be implemented when you will create some files like fanX_target
(Because this file has to be in RPM and you need to convert the RPM into ticks and
write it back to the "target temp" register. On the other hand it will mean that
user receive nonsence when reading from tempX_target
I think I'm missing the whole point of RPM cruise. To me it seems I can
manually setup the requested RPM through the pwm file in manual mode.
Can you explain please how the RPM cruise mode is different from that?
Please always CC to the list so others know too ;)
Thanks,
Regards
Rudolf
next prev parent reply other threads:[~2006-03-05 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-04 20:59 [lm-sensors] [PATCH] Add fan control support to W83627EHF Rudolf Marek
2006-03-04 21:17 ` David Hubbard
2006-03-04 21:47 ` Rudolf Marek
2006-03-05 9:52 ` Rudolf Marek [this message]
2006-03-05 16:42 ` David Hubbard
2006-03-05 20:05 ` Rudolf Marek
2006-03-05 21:10 ` David Hubbard
2006-03-05 21:14 ` 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=440AB4D2.4020806@sh.cvut.cz \
--to=r.marek@sh.cvut.cz \
--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.