From: r.marek@sh.cvut.cz (Rudolf Marek)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] W83792D & Overtemperature LED on Supermicro
Date: Fri, 08 Jul 2005 12:28:22 +0000 [thread overview]
Message-ID: <42CE5527.1050203@sh.cvut.cz> (raw)
In-Reply-To: <1120167411.32695.31.camel@wiz.dev.aspsys.com>
Hi again.
>
> 0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
> 00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 10: 00 00 64 64 93 00 00 13 00 ff 00 00 05 00 00 b3 ..dd?..?....?..?
> 20: a8 a9 d1 bd 1e c8 d3 2b 25 26 ff af 96 af 96 e2 ???????+%&.?????
> 30: b9 ce a8 2f 13 d9 b1 cc a7 50 4b ed ed ed 1f a6 ???/?????PK?????
> 40: 03 00 20 9f 7f ff ff 33 2f 13 88 80 07 ff 80 5c ?. ??..3/????.?\
^^^^
Both subclients are disabled.
It seems our driver
val = w83792d_read_value(new_client, W83792D_REG_I2C_SUBADDR);
data->lm75[0]->addr = 0x48 + (val & 0x07);
data->lm75[1]->addr = 0x48 + ((val >> 4) & 0x07);
}
Does not expect this. You must be using force_subclients parameter to get around this?!
Maybe setting the subclients reset the chip.
if (data->lm75[0]->addr = data->lm75[1]->addr) {
dev_err(&new_client->dev, "duplicate addresses 0x%x "
"for subclients\n", data->lm75[0]->addr);
err = -ENODEV;
goto ERROR_SC_2;
}
Please make sure you are not using force_subclients param,
To allow driver load comment out calling of w83792d_detect_subclients.
Regards
Rudolf
next prev parent reply other threads:[~2005-07-08 12:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 23:37 [lm-sensors] W83792D & Overtemperature LED on Supermicro Eric J. Bowersox
2005-06-30 23:51 ` Eric J. Bowersox
2005-07-01 2:33 ` Mark Studebaker
2005-07-01 17:44 ` Eric J. Bowersox
2005-07-02 18:37 ` Rudolf Marek
2005-07-06 17:41 ` Eric J. Bowersox
2005-07-07 21:19 ` Jean Delvare
2005-07-07 21:26 ` Jean Delvare
2005-07-07 22:11 ` Rudolf Marek
2005-07-08 0:22 ` Eric J. Bowersox
2005-07-08 9:42 ` Rudolf Marek
2005-07-08 12:28 ` Rudolf Marek [this message]
2005-07-08 18:19 ` Eric J. Bowersox
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=42CE5527.1050203@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.