From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] dme1737 0-002e: Write to register 0x30 failed!
Date: Mon, 01 Oct 2007 21:50:26 +0000 [thread overview]
Message-ID: <20071001235026.09c55243@hyperion.delvare> (raw)
In-Reply-To: <1642847378@web.de>
Hi Juerg,
On Mon, 1 Oct 2007 14:39:44 -0700, Juerg Haefliger wrote:
> Aha, that explains it. Can you apply the attached patch and reload the
> driver? Could you also please post the output of 'lsmod'?
>
> ...juerg
>
> --- dme1737.c.orig 2007-10-01 14:34:13.508278000 -0700
> +++ dme1737.c 2007-10-01 14:35:14.041684000 -0700
> @@ -493,8 +493,8 @@ static u8 dme1737_read(struct i2c_client
>
> if (val < 0) {
> dev_warn(&client->dev, "Read from register "
> - "0x%02x failed! Please report to the driver "
> - "maintainer.\n", reg);
> + "0x%02x failed (%d)! Please report to the "
> + "driver maintainer.\n", reg, val);
> }
> } else { /* ISA device */
> outb(reg, client->addr);
> @@ -513,8 +513,8 @@ static s32 dme1737_write(struct i2c_clie
>
> if (res < 0) {
> dev_warn(&client->dev, "Write to register "
> - "0x%02x failed! Please report to the driver "
> - "maintainer.\n", reg);
> + "0x%02x failed (%d)! Please report to the "
> + "driver maintainer.\n", reg, res);
> }
> } else { /* ISA device */
> outb(reg, client->addr);
Unfortunately, most SMBus master drivers return "-1" on error rather
than a sensible error code, so this probably won't help you much. You
would have to fix the underlying bus driver too - this needs to be done
someday anyway.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2007-10-01 21:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 19:08 [lm-sensors] dme1737 0-002e: Write to register 0x30 failed! Juergen Bausa
2007-10-01 17:44 ` Juerg Haefliger
2007-10-01 19:22 ` Juergen Bausa
2007-10-01 21:39 ` Juerg Haefliger
2007-10-01 21:50 ` Jean Delvare [this message]
2007-10-08 18:31 ` Juergen Bausa
2007-10-09 7:03 ` Jean Delvare
2007-10-09 16:08 ` Juerg Haefliger
2007-10-09 19:41 ` Juergen Bausa
2007-10-10 17:12 ` Juerg Haefliger
2007-10-11 7:45 ` Jean Delvare
2007-10-17 18:56 ` Juergen Bausa
2007-10-17 19:43 ` Juerg Haefliger
2007-10-17 21:32 ` Jean Delvare
2007-10-18 4:53 ` Juerg Haefliger
2007-10-19 15:07 ` Jean Delvare
2007-10-20 19:28 ` Juergen Bausa
2007-10-20 19:39 ` Juergen Bausa
2007-10-21 18:40 ` Mark M. Hoffman
2007-10-21 19:14 ` Jean Delvare
2007-10-21 19:37 ` Jean Delvare
2007-10-22 16:02 ` Juerg Haefliger
2007-10-22 16:05 ` Juerg Haefliger
2007-10-23 12:08 ` Jean Delvare
2007-10-23 12:22 ` Jean Delvare
2007-10-23 20:44 ` Juergen Bausa
2007-10-23 21:54 ` Rudolf Marek
2007-10-24 8:48 ` Jean Delvare
2007-10-29 21:23 ` Rudolf Marek
2007-10-30 2:52 ` Juerg Haefliger
2007-10-31 2:40 ` Juerg Haefliger
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=20071001235026.09c55243@hyperion.delvare \
--to=khali@linux-fr.org \
--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.