public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org, sensors@stimpy.netroedge.com
Subject: [PATCH] I2C fixes for 2.6.10-rc2
Date: Tue, 30 Nov 2004 16:13:38 -0800	[thread overview]
Message-ID: <11018600181498@kroah.com> (raw)
In-Reply-To: <20041201001245.GA27535@kroah.com>

ChangeSet 1.2223.2.1, 2004/11/24 14:24:06-08:00, khali@linux-fr.org

[PATCH] I2C: More verbose w83l785ts driver

This simple patch increases the verbosity of the w83l785ts hardware
monitoring driver. I wrote it months ago in the hope it would help solve
a reported problem [1]. Not sure whether it did (no news from user since
July), but the extra debug info may help in the future and doesn't hurt
otherwise, so let's have this in for every user (not that many AFAIK),
just in case.


[1] http://bugzilla.kernel.org/show_bug.cgi?id=2899

Signed-off-by: Jean Delvare <khali@linux-fr.org>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>


 drivers/i2c/chips/w83l785ts.c |    9 ++++++---
 1 files changed, 6 insertions(+), 3 deletions(-)


diff -Nru a/drivers/i2c/chips/w83l785ts.c b/drivers/i2c/chips/w83l785ts.c
--- a/drivers/i2c/chips/w83l785ts.c	2004-11-30 16:01:27 -08:00
+++ b/drivers/i2c/chips/w83l785ts.c	2004-11-30 16:01:27 -08:00
@@ -280,14 +280,17 @@
 	 * default value requested by the caller. */
 	for (i = 1; i <= MAX_RETRIES; i++) {
 		value = i2c_smbus_read_byte_data(client, reg);
-		if (value >= 0)
+		if (value >= 0) {
+			dev_dbg(&client->dev, "Read 0x%02x from register "
+				"0x%02x.\n", value, reg);
 			return value;
+		}
 		dev_dbg(&client->dev, "Read failed, will retry in %d.\n", i);
 		msleep(i);
 	}
 
-	dev_err(&client->dev, "Couldn't read value from register. "
-		"Please report.\n");
+	dev_err(&client->dev, "Couldn't read value from register 0x%02x. "
+		"Please report.\n", reg);
 	return defval;
 }
 


  reply	other threads:[~2004-12-01  0:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01  0:12 [BK PATCH] I2C fixes for 2.6.10-rc2 Greg KH
2004-12-01  0:13 ` Greg KH [this message]
2004-12-01  0:13   ` [PATCH] " Greg KH
2004-12-01  0:13     ` Greg KH
2004-12-01  0:13       ` Greg KH
2004-12-01  0:13         ` Greg KH
2004-12-01  0:13           ` Greg KH
2004-12-01  0:13             ` Greg KH
2004-12-01  0:13               ` Greg KH
2004-12-01  0:13                 ` Greg KH
2004-12-01  0:13                   ` Greg KH
2004-12-01  0:13                     ` Greg KH
2004-12-01  0:13                       ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2004-11-19 21:59 [BK PATCH] " Greg KH
2004-11-19 22:00 ` [PATCH] " Greg KH
2004-11-19 22:00   ` Greg KH
2004-11-19 22:00     ` Greg KH
2004-11-19 22:00       ` Greg KH
2004-11-19 22:01         ` Greg KH

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=11018600181498@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sensors@stimpy.netroedge.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox