All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Brian Willis <willis@arlut.utexas.edu>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] LM75: "ERROR: Can't get temperature data!"
Date: Wed, 07 Nov 2007 00:45:06 +0000	[thread overview]
Message-ID: <1194396306.8090.22.camel@louie> (raw)
In-Reply-To: <1194039013.25315.2.camel@louie>

On Tue, 2007-11-06 at 22:51 +0100, Jean Delvare wrote:
> Unrelated to your problem, but it seems to me that your clock is slightly off ;)
Just slightly :) I just haven't set up my ntp server yet. 

> But this one does not! The attributes are in a subdirectory ("lm75")
> instead of being directly in the device's directory. libsensors doesn't
> expect this and fails. The lm75 driver in the vanilla kernel does NOT
> do this, so I suspect that you're using a modified driver.
I am using the LM75 driver that comes with the Denx embedded linux
kernel. I found the place in the LM75 driver (drivers/hwmon/lm75.c)
where it specifies the attributes to be placed in a separate folder: 

static const struct attribute_group lm75_group = {
	
	//don't put attritube files in a separate folder
	//.name  = "lm75",
	.attrs = lm75_attributes,
};

Commenting out the .name line fixes the problem and I can now read
temperature data from the LM75. 

Thank you so much for all of your help! I'm very glad to get this issue
resolved. 

Regards, 

Michael Willis
Applied Research Labs - University of Texas
willis <at> arlut . utexas . edu






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

  parent reply	other threads:[~2007-11-07  0:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 21:30 [lm-sensors] LM75: "ERROR: Can't get temperature data!" Michael Brian Willis
2007-11-03 18:25 ` Jean Delvare
2007-11-06 18:10 ` Michael Brian Willis
2007-11-06 21:51 ` Jean Delvare
2007-11-07  0:45 ` Michael Brian Willis [this message]
2007-11-09 13:19 ` Jean Delvare
2007-11-17 10:36 ` Heiko Schocher

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=1194396306.8090.22.camel@louie \
    --to=willis@arlut.utexas.edu \
    --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.