From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Hu Mingkai-B21284 <B21284-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: How the lm-sensors communicate with the device driver
Date: Tue, 21 Oct 2008 13:14:49 +0200 [thread overview]
Message-ID: <20081021131449.32d4b429@hyperion.delvare> (raw)
In-Reply-To: <CF6163088BDE8747873ADAA4AF922BF258D527-6lxYB4K41cniD3AT8lUqWFjVikpgYyvb5NbjCUgZEJk@public.gmane.org>
Hi Vincent,
On Tue, 21 Oct 2008 18:31:07 +0800, Hu Mingkai-B21284 wrote:
> I wrote a MCP3021's driver using the new I2C device model under Linux
> 2.6.26.
> The chip MCP3021 is connected to Freescale's I2C controller.
> Now it works well, the following is the log info:
>
> -sh-2.05b# ls /sys/bus/i2c/drivers/mcp3021/
> 0-004d 1-004d bind module uevent unbind
> -sh-2.05b#
>
> -sh-2.05b# cat /sys/bus/i2c/drivers/mcp3021/0-004d/name
> mcp3021
> -sh-2.05b# cat /sys/bus/i2c/drivers/mcp3021/0-004d/in0_input
> 213
> -sh-2.05b# cat /sys/bus/i2c/drivers/mcp3021/0-004d/in0_max
> 213
> -sh-2.05b# cat /sys/bus/i2c/drivers/mcp3021/0-004d/in0_min
> 192
> -sh-2.05b# cat /sys/bus/i2c/drivers/mcp3021/0-004d/curr1_input
> 960
> -sh-2.05b# cat /sys/bus/i2c/drivers/mcp3021/0-004d/curr1_max
> 1065
> -sh-2.05b# cat /sys/bus/i2c/drivers/mcp3021/0-004d/curr1_min
> 945
>
> -sh-2.05b# sensors
> mcp3021-i2c-0-4d
>
> Adapter: MPC adapter
> in0: +0.21 V (min = +0.19 V, max = +0.22 V)
>
> mcp3021-i2c-1-4d
> Adapter: MPC adapter
> in0: +0.41 V (min = +0.41 V, max = +0.41 V)
>
> Q:
> 1. How the lm-sensors communicate with the device driver?
> 2. How the lm-sensors get the attribute info?
> 2. Why the current info, i.e. curr1_x, doesn't list ?
Wrong mailing list. Questions about lm-sensors go to the lm-sensors
mailing list:
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
--
Jean Delvare
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
prev parent reply other threads:[~2008-10-21 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 10:31 How the lm-sensors communicate with the device driver Hu Mingkai-B21284
[not found] ` <CF6163088BDE8747873ADAA4AF922BF258D527-6lxYB4K41cniD3AT8lUqWFjVikpgYyvb5NbjCUgZEJk@public.gmane.org>
2008-10-21 11:14 ` Jean Delvare [this message]
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=20081021131449.32d4b429@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=B21284-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox