All of lore.kernel.org
 help / color / mirror / Atom feed
From: J.Kilb@gmx.de (Juergen Kilb)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] ADT7475
Date: Sat, 02 Sep 2006 19:10:49 +0000	[thread overview]
Message-ID: <200609022110.49511.J.Kilb@gmx.de> (raw)
In-Reply-To: <20060902193444.a259efdb.khali@linux-fr.org>

Hi Jean,

> Hi Juergen,
>
> > it seems that the ADT7475 is compatible with an ADT7463, so i have tried
> > to use the lm85 driver. (The ADT7475 is missing the Vid Inputs.)
>
> How did you figure out? I guess you mean the "vin inputs"? VID inputs
> are something different. Oh well, they are also missing, anyway.
>
I have found that the lm85 driver is usable for the ADT7463, then i thought 
there could be a possibility that the ADT7475 is compatible with the ADT7463 
in some way.  
After that i have compared nearly every page of the two datasheets....  
If you take a look at the functional diagram of the ADT7463

http://www.analog.com/images/Product_Descriptions/408124366940429ADT7463_S.jpg

you can see in the upper left corner 7 "VID" Inputs which are not available at 
the ADT7475.

> Replace ":" with "=", and it should work better, except that according
> to the output below, the proper address is 1,0x2e rather than 0,0x2e.
>
OK...

> Do the fan speeds reported here match the ones displayed by your BIOS?
> Can you try setting limits and checking whether alarms trigger as they
> should?
>
Yes they do.. i think good enough ;-)

			Bios		Sensors
CHA_FAN2	1427		1420 (fan2)
CHA_FAN3	1908	1889 (fan3)
CHA_FAN4	1978	2019 (CPU_FAN)

> The temp2 value is rather frightening... It is supposed to be the
> chip's own temperature. It looks like the chip supports different modes,
> include an "ADT7463 compatibility mode", and I guess your chip is not
> in this mode, thus the weird reading. The external temperatures are
> obviously not wired.
>
> Now the question is, do we want to add support for the ADT7475 chip to
> the lm85 driver? That's a recurring question, each time several chips
> are compatible but still somewhat different.
>
> In this case, the lm85 driver already supports 6 different chips
> (although there was no reason to differenciate between the B and C
> revisions as far as I can see) and we must beware of not increasing the
> complexity of our drivers beyond reason. I'm not too sure what to do.
> Maybe we can try adding support to the lm85 driver, and if it turns up
> adding too much complexity, do a separate driver.
>
Yes i think, this would be the right way.

> One element which may help us decide is whether the ADT7475 itself is
> compatible with other chips. If it is, making a new driver for the
> ADT7475 and the compatible chips would make sense. Can you make some
> research?
Yes i can do some research... but i've not much spare time at the moment and i 
am on vacation for 3 weeks starting next friday.

=
Juergen


  reply	other threads:[~2006-09-02 19:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-02 17:34 [lm-sensors] ADT7475 Jean Delvare
2006-09-02 19:10 ` Juergen Kilb [this message]
2006-09-26 20:32 ` Len J. White
2007-01-27 12:44 ` Diggory Hardy
2007-07-06 20:44 ` Joel McKee Cooper
2007-07-07  7:26 ` Hans de Goede

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=200609022110.49511.J.Kilb@gmx.de \
    --to=j.kilb@gmx.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.