All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: Justin Thiessen <jthiessen@penguincomputing.com>
Cc: sensors@Stimpy.netroedge.com, linux-kernel@vger.kernel.org,
	Greg KH <greg@kroah.com>
Subject: adm1026 driver port for kernel 2.6.X - [REVISED DRIVER]
Date: Thu, 19 May 2005 06:25:21 +0000	[thread overview]
Message-ID: <20041102203122.7e7a8366.khali@linux-fr.org> (raw)
In-Reply-To: <20041102164642.GA16378@penguincomputing.com>

Hi justin,

> As discussed in previous messages, control over the pwm output is
> provided via:
> 
> pwm1                  {0-255}
> pwm1_auto_pwm_min     {0-255}

What exactly does this value represent again? (See below too.)

> pwm1_enable           {0-2}  (off, manual, automatic fan control)
> 
> Access to the DAC is provided via:
> 
> analog_out            {0-2500} (millivolts)
> 
> No way is currently provided to turn on DAC-mediated automatic fan
> control. See my previous email in this thread for the reasons why.

On a side note, MBM lists the ADM1026 as being used on only two
motherboard models, one being yours. Considering this and the fact that
nobody ever requested us to port the adm1026 driver to Linux 2.6, I
would conclude that the motherboard you use is possibly the only one
worth supporting. Do not bother with anything that you don't personally
need. We can still add it later on request.

> Control over automatic fan "on" temperatures are provided by:
> 
> temp[1-3]_auto_point1_temp     {-128000 - 127000}
> 
> Hardware-determined hysteresis and range values are revealed in:
> 
> temp[1-3]_auto_point1_temp_hyst   {-6000}

Hysteresis temperatures have to be absolute temperatures as per
interface standard.

> temp[1-3]_auto_point2_temp        {temp[1-3]_auto_point1_temp + 20000}

I'm a bit surprised not to see temp[1-3]_auto_point[1-2]_pwm. Trip
points are supposed to be (temp, pwm) pairs. Doesn't pwm1_auto_pwm_min
above correspond to one or more of these?

> Failsafe critical temperatures at which the fans go to maximum speed
> are controled via:
> 
> temp_crit_enable       {0-1}  (off, on)
> temp[1-3]_crit         {-128000 - 127000}

Granted it's not part of the standard yet, but you would have three
files temp[1-3]_crit_enable if we stick to our chip-indenpendent
interface logic. Either make 1 read-write and [2-3] read-only, or make
all read-write and each one changes the three values.

> These values override any values set for the pwm-mediated automatic
> fan control.

Doesn't this mean that you could integrate these in the auto-pwm
interface as point3?

> Thanks to all for the feedback.

You're welcome. Sorry to ask questions about the proposed interface
again, I just want things to be as clean and logical as possible.

Thanks,

-- 
Jean Delvare
http://khali.linux-fr.org/

WARNING: multiple messages have this Message-ID (diff)
From: Jean Delvare <khali@linux-fr.org>
To: Justin Thiessen <jthiessen@penguincomputing.com>
Cc: sensors@Stimpy.netroedge.com, linux-kernel@vger.kernel.org,
	Greg KH <greg@kroah.com>
Subject: Re: adm1026 driver port for kernel 2.6.X - [REVISED DRIVER]
Date: Tue, 2 Nov 2004 20:31:22 +0100	[thread overview]
Message-ID: <20041102203122.7e7a8366.khali@linux-fr.org> (raw)
In-Reply-To: <20041102164642.GA16378@penguincomputing.com>

Hi justin,

> As discussed in previous messages, control over the pwm output is
> provided via:
> 
> pwm1                  {0-255}
> pwm1_auto_pwm_min     {0-255}

What exactly does this value represent again? (See below too.)

> pwm1_enable           {0-2}  (off, manual, automatic fan control)
> 
> Access to the DAC is provided via:
> 
> analog_out            {0-2500} (millivolts)
> 
> No way is currently provided to turn on DAC-mediated automatic fan
> control. See my previous email in this thread for the reasons why.

On a side note, MBM lists the ADM1026 as being used on only two
motherboard models, one being yours. Considering this and the fact that
nobody ever requested us to port the adm1026 driver to Linux 2.6, I
would conclude that the motherboard you use is possibly the only one
worth supporting. Do not bother with anything that you don't personally
need. We can still add it later on request.

> Control over automatic fan "on" temperatures are provided by:
> 
> temp[1-3]_auto_point1_temp     {-128000 - 127000}
> 
> Hardware-determined hysteresis and range values are revealed in:
> 
> temp[1-3]_auto_point1_temp_hyst   {-6000}

Hysteresis temperatures have to be absolute temperatures as per
interface standard.

> temp[1-3]_auto_point2_temp        {temp[1-3]_auto_point1_temp + 20000}

I'm a bit surprised not to see temp[1-3]_auto_point[1-2]_pwm. Trip
points are supposed to be (temp, pwm) pairs. Doesn't pwm1_auto_pwm_min
above correspond to one or more of these?

> Failsafe critical temperatures at which the fans go to maximum speed
> are controled via:
> 
> temp_crit_enable       {0-1}  (off, on)
> temp[1-3]_crit         {-128000 - 127000}

Granted it's not part of the standard yet, but you would have three
files temp[1-3]_crit_enable if we stick to our chip-indenpendent
interface logic. Either make 1 read-write and [2-3] read-only, or make
all read-write and each one changes the three values.

> These values override any values set for the pwm-mediated automatic
> fan control.

Doesn't this mean that you could integrate these in the auto-pwm
interface as point3?

> Thanks to all for the feedback.

You're welcome. Sorry to ask questions about the proposed interface
again, I just want things to be as clean and logical as possible.

Thanks,

-- 
Jean Delvare
http://khali.linux-fr.org/

  reply	other threads:[~2005-05-19  6:25 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19  6:25 adm1026 driver port for kernel 2.6.X Justin Thiessen
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Justin Thiessen
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Justin Thiessen
2005-05-19  6:25 ` Mark M. Hoffman
2005-05-19  6:25 ` Justin Thiessen
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Justin Thiessen
2004-11-02 16:46   ` adm1026 driver port for kernel 2.6.X - [REVISED DRIVER] Justin Thiessen
2005-05-19  6:25     ` Justin Thiessen
2004-11-02 19:31     ` Jean Delvare [this message]
2005-05-19  6:25       ` Jean Delvare
2004-11-02 22:17       ` Justin Thiessen
2005-05-19  6:25         ` Justin Thiessen
2004-11-03  8:01         ` Jean Delvare
2005-05-19  6:25           ` Jean Delvare
2004-11-03 16:43           ` adm1026 driver port for kernel 2.6.X - [RE-REVISED DRIVER] Justin Thiessen
2005-05-19  6:25             ` Justin Thiessen
2004-11-16 18:56             ` Jean Delvare
2005-05-19  6:25               ` Jean Delvare
2004-11-18 18:56             ` adm1026 driver port for kernel 2.6.10-rc2 " Justin Thiessen
2005-05-19  6:25               ` Justin Thiessen
2004-11-20  9:57               ` Jean Delvare
2005-05-19  6:25                 ` Jean Delvare
2004-11-22 19:35                 ` Justin Thiessen
2005-05-19  6:25                   ` Justin Thiessen
2004-11-20 10:13               ` Arjan van de Ven
2005-05-19  6:25                 ` Arjan van de Ven
2004-11-20 10:32                 ` Jean Delvare
2005-05-19  6:25                   ` Jean Delvare
2004-11-22 19:43                 ` Justin Thiessen
2005-05-19  6:25                   ` Justin Thiessen
2004-11-22 21:00                   ` Arjan van de Ven
2005-05-19  6:25                     ` Arjan van de Ven
2004-11-22 21:30                     ` linux-os
2005-05-19  6:25                       ` linux-os
2004-11-23 17:58                   ` Jean Delvare
2005-05-19  6:25                     ` Jean Delvare
2004-11-23 16:52               ` adm1026 driver port for kernel 2.6.10-rc2 (patch includes driver, patch to Kconfig, and patch to Makefile) Justin Thiessen
2005-05-19  6:25                 ` adm1026 driver port for kernel 2.6.10-rc2 (patch includes driver, Justin Thiessen
2004-11-23 17:50                 ` adm1026 driver port for kernel 2.6.10-rc2 (patch includes driver, patch to Kconfig, and patch to Makefile) Jean Delvare
2005-05-19  6:25                   ` adm1026 driver port for kernel 2.6.10-rc2 (patch includes Jean Delvare
2004-11-24 21:36                 ` adm1026 driver port for kernel 2.6.10-rc2 (patch includes driver, patch to Kconfig, and patch to Makefile) Greg KH
2005-05-19  6:25                   ` adm1026 driver port for kernel 2.6.10-rc2 (patch includes driver, Greg KH
2004-11-24 23:10                   ` adm1026 driver port for kernel 2.6.10-rc2 (patch includes driver, patch to Kconfig, and patch to Makefile) [fixed] Justin Thiessen
2005-05-19  6:25                     ` adm1026 driver port for kernel 2.6.10-rc2 (patch includes Justin Thiessen
2004-11-24 22:35                     ` adm1026 driver port for kernel 2.6.10-rc2 (patch includes driver, patch to Kconfig, and patch to Makefile) [fixed] Greg KH
2005-05-19  6:25                       ` adm1026 driver port for kernel 2.6.10-rc2 (patch includes driver, Greg KH
2005-05-19  6:25 ` adm1026 driver port for kernel 2.6.X Jean Delvare

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=20041102203122.7e7a8366.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=greg@kroah.com \
    --cc=jthiessen@penguincomputing.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sensors@Stimpy.netroedge.com \
    /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.