From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Feng Tang <feng.tang@intel.com>
Cc: Jean Delvare <khali@linux-fr.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
"Ben Dooks (embedded platforms)" <ben-linux@fluff.org>,
Tomoya MORINAGA <tomoya.rohm@gmail.com>
Subject: Re: i2c-eg20t: regression since i2c_add_numbered_adapter change
Date: Thu, 30 Aug 2012 13:08:09 +0200 [thread overview]
Message-ID: <6208908.ZjG7eB9lJn@ws-stein> (raw)
In-Reply-To: <20120830171915.36b6d10b@feng-i7>
On Thursday 30 August 2012 17:19:15, Feng Tang wrote:
> > IMO the i2c_register_board_info only works in quite static setups. Especially with I2C-Busses attached to hotplugable PCI devices this way doesn't work reliable any more.
> > The device come and go dynamically so you can't assume fixed mapping.
>
> Can you specify the hotplugable?
> 1. A hotplugable i2c bus controller (say i2c_eg20t) with all fixed i2c
> devices connecting to it
> 2. i2c bus controller is fixed, while the i2c devices will be dynamically
> connected to it.
> 3. Both the bus controller and devices are dynamically hotplugged
I had scenario 1 in mind, but with more than 1 bus controller (say 2x i2c_eg20t). How can you set a fixed numbering if there are more controllers, each with maybe more than 1 bus?
Anyway, how can you provide a static bus numbering if there are more than one driver or more than one device per driver if the devices are hotplugable?
Best regards,
Alexander
next prev parent reply other threads:[~2012-08-30 11:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 6:30 i2c-eg20t: regression since i2c_add_numbered_adapter change Alexander Stein
2012-08-22 7:29 ` Feng Tang
2012-08-22 7:57 ` Alexander Stein
2012-08-22 8:04 ` Feng Tang
2012-08-22 9:17 ` Alexander Stein
2012-08-23 8:28 ` Feng Tang
2012-08-29 18:40 ` Jean Delvare
2012-08-30 7:49 ` Alexander Stein
2012-08-30 9:19 ` Feng Tang
2012-08-30 11:08 ` Alexander Stein [this message]
2012-08-31 2:16 ` Feng Tang
2012-09-08 13:18 ` Jean Delvare
2012-08-30 9:10 ` Feng Tang
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=6208908.ZjG7eB9lJn@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=ben-linux@fluff.org \
--cc=feng.tang@intel.com \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tomoya.rohm@gmail.com \
/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