From: Guenter Roeck <guenter.roeck-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: "linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Michael Lawnick <ml.lawnick-Mmb7MZpHnFY@public.gmane.org>,
Rodolfo Giometti
<giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org>
Subject: Re: Driver for pca9541 bus master selector
Date: Wed, 13 Oct 2010 09:05:16 -0700 [thread overview]
Message-ID: <20101013160515.GA15081@ericsson.com> (raw)
In-Reply-To: <20100929135401.GA11771-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>
On Wed, Sep 29, 2010 at 03:19:28AM -0400, Jean Delvare wrote:
[ ... ]
> I don't quite see the point of such chips, BTW. I2C supports
> multi-master already, so two masters talking to the same slave
> sequentially is already supported.
To follow up on this, turns out there are (at least) two good reasons for having
such a chip.
First, not all i2c masters support multi-master configuration.
The second reason is much more important. In a redundant system, one would not
want redundant masters to be on the same i2c bus. If one of the two fails and
blocks the bus, access to all slaves would be blocked. Not a good idea. Much
better to have two i2c busses, and select the current master on the slave side.
Turns out both reasons apply in my use case. Testing shows that master selection
works quite well with the driver I just submitted. I can persistently access all
slaves from both masters even under high contention (both masters trying to
access the same slave at the same time). If one of the masters fails while
having access to the connected slaves, the other simply takes over after
arbitration times out.
Guenter
next prev parent reply other threads:[~2010-10-13 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 14:33 Driver for pca9541 bus master selector Guenter Roeck
[not found] ` <20100928143302.GA7593-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>
2010-09-28 15:16 ` Jean Delvare
[not found] ` <20100928171607.395f7736-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2010-09-28 16:07 ` Guenter Roeck
[not found] ` <20100928160746.GB7976-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>
2010-09-28 16:42 ` Jean Delvare
[not found] ` <20100928184215.00f82717-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2010-09-28 17:16 ` Guenter Roeck
[not found] ` <20100928171627.GA8415-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>
2010-09-29 7:19 ` Jean Delvare
[not found] ` <20100929091928.16256bb7-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2010-09-29 13:54 ` Guenter Roeck
[not found] ` <20100929135401.GA11771-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org>
2010-09-30 5:59 ` Michael Lawnick
[not found] ` <4CA42750.5020500-Mmb7MZpHnFY@public.gmane.org>
2010-09-30 7:48 ` Guenter Roeck
2010-10-13 16:05 ` Guenter Roeck [this message]
2010-10-13 15:45 ` Guenter Roeck
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=20101013160515.GA15081@ericsson.com \
--to=guenter.roeck-izefyvvap7pwk0htik3j/w@public.gmane.org \
--cc=giometti-AVVDYK/kqiJWk0Htik3J/w@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ml.lawnick-Mmb7MZpHnFY@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