From: Hartmut Knaack <knaack.h-Mmb7MZpHnFY@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: i2c gpio expander on hotplug i2c-adapter
Date: Tue, 07 Jun 2011 23:59:17 +0200 [thread overview]
Message-ID: <4DEE9F35.9020606@gmx.de> (raw)
Hi there,
I'm a bit puzzled. My desired setup is something like this: Linux
station => usb i2c-adapter (i2c tiny usb) => i2c switch (pca9548) => i2c
gpio expander (pca9555)
So far, instantiation works for the i2c switch using the sysfs method
(echo pca9548 0x70 > /sys/bus/i2c....). What's really causing me
troubles is instantiating the pca9555. What I found so far indicates
that it has to be defined in the machine specific file. So that is what
I already added:
static struct pca953x_platform_data pca9555_0 = {
.gpio_base = 32,
};
static struct i2c_board_info __initdata i2c_tiny_board_info[] = {
{
I2C_BOARD_INFO("pca9555",0x21),
.platform_data = &pca9555_0,
}
};
Now I'm struggling how to declare my i2c tiny usb adapter to be the bus
where the pca9555 should live on (leaving out the i2c switch for the
moment). What I tried so far did not work (obviously):
static struct platform_device i2c_tiny_usb_device = {
.name = "i2c-tiny-usb",
.id = 0,
};
static void __devinit i2c_tiny_usb_init(void)
{
i2c_register_board_info(0,i2c_tiny_board_info,
ARRAY_SIZE(i2c_tiny_board_info));
platform_device_register(&i2c_tiny_usb_device);
};
The i2c_tiny_usb_init() funciton gets called in the init section. It
compiles without errors, but with this kernel, the i2c-adapter now gets
registered as i2c-1. How would a proper declaration of that i2c-adapter
look like? Or would there even be a chance to do that instantiation from
a userspace program? I saw that the symbol "pca9555_0" is listed in the
system.map file of that kernel. So, would there even be a chance to just
declare the gpio platform data in the kernel and do the instantiation in
userspace?
Thanks in advance,
Hartmut
reply other threads:[~2011-06-07 21:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DEE9F35.9020606@gmx.de \
--to=knaack.h-mmb7mzphnfy@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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 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.