From: Rodolfo Giometti <giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
To: Felix Radensky <felix-L1vi/lXTdtvUXIAPrk8Z/A@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH 1/3] i2c: virtual i2c adapter support
Date: Mon, 27 Oct 2008 09:20:25 +0100 [thread overview]
Message-ID: <20081027082025.GC11339@tekkaman> (raw)
In-Reply-To: <4904E6F3.50609-L1vi/lXTdtvUXIAPrk8Z/A@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1962 bytes --]
On Sun, Oct 26, 2008 at 11:53:55PM +0200, Felix Radensky wrote:
> Hi, Rodolfo
>
> I've tried your patches with linux-2.6.27 kernel running
> on custom board with 460EX PowerPC. This board has
> two i2c buses and pca9548 switch on bus 0.
Please, consider thay my patch has been *not* accepted into main line
due a mutex problem... :'(
> My question is: how can I register board i2c devices behind
> the mux in board init code, and make them properly identified
> when relevant drivers are loaded.
I have just defined the i2c devices behind the mux as connected to the
new virtual adapters:
static int wr1100_adap_ids[] = {
2, 3,
};
static struct pca954x_platform_data wr1100_i2cmux_adap_ids = {
.adap_ids = wr1100_adap_ids,
.len = ARRAY_SIZE(wr1100_adap_ids),
};
static struct i2c_board_info __initdata wr1100_i2c_devices[] = {
{
I2C_BOARD_INFO("pca9540", 0x70),
.platform_data = &wr1100_i2cmux_adap_ids,
},
};
static struct i2c_board_info __initdata wr1100_i2c_mux_devices[] = {
{
I2C_BOARD_INFO("bq27200", 0x55),
},
};
Then into machine startup code:
i2c_register_board_info(0, wr1100_i2c_devices,
ARRAY_SIZE(wr1100_i2c_devices));
i2c_register_board_info(2, wr1100_i2c_mux_devices,
ARRAY_SIZE(wr1100_i2c_mux_devices));
i2c_register_board_info(3, wr1100_i2c_mux_devices,
ARRAY_SIZE(wr1100_i2c_mux_devices));
Ciao,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org
Linux Device Driver giometti-k2GhghHVRtY@public.gmane.org
Embedded Systems phone: +39 349 2432127
UNIX programming skype: rodolfo.giometti
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-10-27 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 21:53 [PATCH 1/3] i2c: virtual i2c adapter support Felix Radensky
[not found] ` <4904E6F3.50609-L1vi/lXTdtvUXIAPrk8Z/A@public.gmane.org>
2008-10-27 8:20 ` Rodolfo Giometti [this message]
2008-10-27 11:31 ` Felix Radensky
2008-10-27 11:31 ` Felix Radensky
[not found] ` <4905A68D.7040708-L1vi/lXTdtvUXIAPrk8Z/A@public.gmane.org>
2008-10-27 11:52 ` Rodolfo Giometti
-- strict thread matches above, loose matches on Subject: below --
2008-06-18 13:06 Rodolfo Giometti
[not found] ` <1213794365-8089-1-git-send-email-giometti-k2GhghHVRtY@public.gmane.org>
2008-06-18 19:00 ` Ben Dooks
[not found] ` <20080618190008.GK10351-SMNkleLxa3Z6Wcw2j4pizdi2O/JbrIOy@public.gmane.org>
2008-06-19 12:25 ` Rodolfo Giometti
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=20081027082025.GC11339@tekkaman \
--to=giometti-avvdyk/kqijwk0htik3j/w@public.gmane.org \
--cc=felix-L1vi/lXTdtvUXIAPrk8Z/A@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 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.