* Velleman K8000
@ 2009-09-12 16:39 Kari Laine
[not found] ` <61452b690909120939kcc61779vfb7e686a40276ef7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
0 siblings, 1 reply; 2+ messages in thread
From: Kari Laine @ 2009-09-12 16:39 UTC (permalink / raw)
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA
Hi Jean
thank you very much for good information.
Hopefully you can answer these questions as well because I am totally lost.
On Sat, Sep 12, 2009 at 12:12 PM, Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> wrote:
> You didn't tell which kernel you are using, but kernel 2.6.17 and later
> wouldn't let you load i2c-parport without a type parameter.
The kernel is 2.6.27
> It doesn't matter. i2c-core gets loaded automatically when any other
> module needs it.
it indeed is.
> You should install i2c-tools and use the command "i2cdetect -l". This
> will tell you what each i2c bus on your system is.
>
> Then you can try "i2cdetect <n>" where <n> is a bus number, to scan the
> bus in question. This is a good way to test whether the driver and
> device are working properly.
it gives this. So it seems to find all four chips on Velleman K8000 .
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- 38 39 -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
>
>> If these devices probably refer to Velleman - then how I can refer
>> different i2c-devices on the board.
>
> Depends on the device. In the case of the Philips PCF8591, which
> apparently you are using, sysfs attributes will be created somewhere
> under /sys/bus/i2c/drivers/pcf8591. Each device has a name of the form
> <bus number>-<device address>, for example "1-0048" for a PCF8591.
When I now do
modprobe pcf8591
In
linux-1fyv:/sys/bus/i2c/devices directory
comes 1-0048
Now I have to figure out how to use this device. Any comments.
The Velleman K8000 card has three other chips which show up in
I2C-bus. Two PCF8574A which are I/O-chips and TDA8444-chip which is
DA-chip. I don't find any modules for them. Does it mean that they are
not supported as of yet or anymore?
>
> The sysfs attributes in question are described in
> Documentation/hwmon/pcf8591 (or Documentation/i2c/chips/pcf8591 on
> kernels older than 2.6.30.)
>
> Hope this helps,
It helped much!
All the best to you
Kari
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Velleman K8000
[not found] ` <61452b690909120939kcc61779vfb7e686a40276ef7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2009-09-12 18:42 ` Jean Delvare
0 siblings, 0 replies; 2+ messages in thread
From: Jean Delvare @ 2009-09-12 18:42 UTC (permalink / raw)
To: Kari Laine; +Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA
Hi Kari,
On Sat, 12 Sep 2009 19:39:25 +0300, Kari Laine wrote:
> thank you very much for good information.
>
> Hopefully you can answer these questions as well because I am totally lost.
>
> On Sat, Sep 12, 2009 at 12:12 PM, Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> wrote:
> > You didn't tell which kernel you are using, but kernel 2.6.17 and later
> > wouldn't let you load i2c-parport without a type parameter.
> The kernel is 2.6.27
>
> > It doesn't matter. i2c-core gets loaded automatically when any other
> > module needs it.
> it indeed is.
>
> > You should install i2c-tools and use the command "i2cdetect -l". This
> > will tell you what each i2c bus on your system is.
> >
> > Then you can try "i2cdetect <n>" where <n> is a bus number, to scan the
> > bus in question. This is a good way to test whether the driver and
> > device are working properly.
> it gives this. So it seems to find all four chips on Velleman K8000 .
>
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: -- -- -- -- -- -- -- -- -- -- -- -- --
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 30: -- -- -- -- -- -- -- -- 38 39 -- -- -- -- -- --
> 40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- --
> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 70: -- -- -- -- -- -- -- --
Looks good.
> >> If these devices probably refer to Velleman - then how I can refer
> >> different i2c-devices on the board.
> >
> > Depends on the device. In the case of the Philips PCF8591, which
> > apparently you are using, sysfs attributes will be created somewhere
> > under /sys/bus/i2c/drivers/pcf8591. Each device has a name of the form
> > <bus number>-<device address>, for example "1-0048" for a PCF8591.
> When I now do
>
> modprobe pcf8591
>
> In
>
> linux-1fyv:/sys/bus/i2c/devices directory
>
> comes 1-0048
>
> Now I have to figure out how to use this device. Any comments.
Have you read the driver's documentation?
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=Documentation/hwmon/pcf8591;hb=HEAD
> The Velleman K8000 card has three other chips which show up in
> I2C-bus. Two PCF8574A which are I/O-chips and TDA8444-chip which is
> DA-chip. I don't find any modules for them. Does it mean that they are
> not supported as of yet or anymore?
The PCF8574A is supported by the pcf8574 driver (or pcf857x on recent
kernels.) I am not aware of a driver for the TDA8444.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-09-12 18:42 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-09-12 16:39 Velleman K8000 Kari Laine
[not found] ` <61452b690909120939kcc61779vfb7e686a40276ef7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-12 18:42 ` Jean Delvare
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.