All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Pattenden <chris@aeryon.com>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Bug Report: Bus substitution causing a problem
Date: Mon, 08 Jul 2013 21:18:46 +0000	[thread overview]
Message-ID: <51DB2CB6.4060303@aeryon.com> (raw)

Howdy,

I'm working to configure lm_sensors and have notice a few strange issues.

I'm working on a TI 8148 on custom hardware.
Linux 2.6.37
lm_sensors lm_sensors-3.3.4

i2cdetect -l shows the following:

	i2c-2   i2c             OMAP I2C adapter                        I2C adapter
	i2c-4   i2c             OMAP I2C adapter                        I2C adapter



I have two TI ADC128D818 ADCs (I cobbled together my own driver while 
waiting for support -- I see that someone else requested the same driver 
last week :-). They are:
	adc128d818-i2c-4-1d
	adc128d818-i2c-4-37

	
"sensors --bus-list" shows the following:
	bus "i2c-4" "OMAP I2C adapter"
Why bus i2c-2 isn't shown, I don't know. That's likely an issue.


I started using the following sensors.conf:
	chip "adc128d818-i2c-4-1d"
	label in0 "Test"

However, I was told that the "bus was unidentified".
I used the following sensors.conf, hoping to fix the problem:
	bus "i2c-4" "OMAP I2C adapter"
	chip "adc128d818-i2c-4-1d"
	label in0 "Test"
However, none in0 was not renamed as expected -- it printed as "in0".

It turns out that sensors_substitute_busses() incorrectly renumbers 
adc128d818-i2c-4-1d to adc128d818-i2c-2-1d and then can't find the 
labels. If I use the following sensors.conf (or comment out the call to 
sensors_substitute_busses()), sensors works as expected:
	chip "adc128d818-i2c-*-1d"
	label in0 "Test"

Am I doing something wrong or is there something strange going on with 
the bus renaming. What is the point of the bus renaming?

Thanks,
Chris


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

         reply	other threads:[~2013-07-08 21:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-08 14:15 [lm-sensors] Displaying Voltage as Temperature?!? Chris Pattenden
2013-07-08 16:51 ` Guenter Roeck
2013-07-08 21:18 ` Chris Pattenden [this message]
2013-07-08 22:00   ` [lm-sensors] Bug Report: Bus substitution causing a problem Jean Delvare
     [not found]     ` <20130709000013.1ca77b1d-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2013-07-08 22:27       ` Guenter Roeck
2013-07-08 22:27         ` Guenter Roeck
     [not found]         ` <20130708222732.GA10676-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
2013-07-09  5:51           ` Jean Delvare
2013-07-09  5:51             ` Jean Delvare

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=51DB2CB6.4060303@aeryon.com \
    --to=chris@aeryon.com \
    --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.