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 09:42:14 +0000 [thread overview]
Message-ID: <42CE2E40.9050609@sh.cvut.cz> (raw)
In-Reply-To: <1120167411.32695.31.camel@wiz.dev.aspsys.com>
Hello,
Something in our driver triggers the whole chip reset. We are not touching the reset bit so it must be
something else. You have revision 13 of the chip and we have datasheet of 12 revision.
I would suggest following:
static int
w83792d_write_value(struct i2c_client *client, u8 reg, u8 value)
{
i2c_smbus_write_byte_data(client, reg, value);
return 0;
}
remove this funcs and replace with this one:
static int
wrt(struct i2c_client *client, u8 reg, u8 value)
{
i2c_smbus_write_byte_data(client, reg, value);
if (i2c_smbus_read_byte_data(client, 0x40)!=3) {
printk("Chip RESET occured when written %x to %x reg\n",value,reg);
}
return 0;
}
And add to top of this file:
#define w83792d_write_value(a,b,c) { printk("write called from line %d\n",__LINE__); wrt(a,b,c) }
So we can track what call it was.
Proposed funcs were not tested but I think you get the idea. Register 0x40 is master config reg. After reset it defaults to value 0x1 and it is before 0x3.
Lets hope the chip will reset when writing into it and not reading by some odd reason.
Regards
Rudolf
next prev parent reply other threads:[~2005-07-08 9:42 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 [this message]
2005-07-08 12:28 ` Rudolf Marek
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=42CE2E40.9050609@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.