All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denny Schierz <linuxmail@4lin.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] G760A not working korrekt on NAS dlink 323 HW C1
Date: Fri, 26 Mar 2010 00:48:11 +0000	[thread overview]
Message-ID: <1269564491.3051.293.camel@mac> (raw)
In-Reply-To: <1269292447.6810.21.camel@kusanagi>


[-- Attachment #1.1: Type: text/plain, Size: 4814 bytes --]

hi,

i was able to locate the chip on the board. His partnumber is AX3106
(PWM controller)

http://www.micro-bridge.com/data/Axelite/AX3106.pdf


Some debug:

nas:~# i2cdetect -l
i2c-0   i2c             mv64xxx_i2c adapter                     I2C
adapter

nas:~# i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and
worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- 0c -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- UU -- 
40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --  


so, that is the output, what now? I contacted the maintainer from the
file dns323-setup.c, but he has no time nor the hardware :-/

any suggestions?

cu denny


nas:~# i2cdump 0 0x0c 
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and
worse!
I will probe file /dev/i2c-0, address 0xc, mode byte
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
10: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
20: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
30: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
40: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
50: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
60: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
70: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
80: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
90: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
a0: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
b0: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
c0: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
d0: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
e0: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????
f0: 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91 91    ????????????????


nas:~# i2cdump 0 0x3 
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and
worse!
I will probe file /dev/i2c-0, address 0x3, mode byte
Continue? [Y/n] 
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
80: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
90: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
a0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
b0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
c0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
d0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
e0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
f0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX


Am Dienstag, den 23.03.2010, 13:43 +0100 schrieb Jean Delvare:
> For the time being, arch/arm/mach-orion5x/dns323-setup.c should
> probably refrain from instantiating a g760a device on revision C1
> boards. You'll have to discuss this with whoever is in charge of this
> file.
> 
> Then you can try running i2cdetect on the I2C adapter, to see if a
> mysterious device has been added. The I2C device map is supposed to
> be:
> 
> /*
>  * On the DNS-323 the following devices are attached via I2C:
>  *
>  *  i2c addr | chip        | description
>  *  0x3e     | GMT G760Af  | fan speed PWM controller
>  *  0x48     | GMT G751-2f | temp. sensor and therm. watchdog (LM75
> compatible)
>  *  0x68     | ST M41T80   | RTC w/ alarm
>  */
> 
> but I guess yours will be different. 

[-- Attachment #1.2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

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

  parent reply	other threads:[~2010-03-26  0:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22 21:14 [lm-sensors] G760A not working korrekt on NAS dlink 323 HW C1 Denny Schierz
2010-03-23 12:43 ` Jean Delvare
2010-03-26  0:48 ` Denny Schierz [this message]
2010-03-29 15:25 ` 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=1269564491.3051.293.camel@mac \
    --to=linuxmail@4lin.net \
    --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.