From: Wolfram Sang <wsa@the-dreams.de>
To: Kachalov Anton <mouse@mayc.ru>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: i2c: slave support framework improvements
Date: Mon, 25 Jul 2016 09:21:51 +0200 [thread overview]
Message-ID: <20160725072151.GA1599@katana> (raw)
In-Reply-To: <27421469430128@web19h.yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
> > How do the other masters know that their channel is currently muxed
> > then? And what if two of them want to access two of your slaves at
> > the same time?
>
> In current implementation this I2C switch might be only switched from
> one side (via i2c command). From the MUX point of view, there is only
> one master (which may mux) and a number of slaves behind each channel.
> But on proto level IPMB requires to act as multi-master to receive
> answers from other intelligent nodes. To receive answer requesting
> node have to switch to slave mode after master write request.
And how is guaranteed that one of the intelligent nodes behind the MUX
do no send requests on their own while their channel is not muxed?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-25 7:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-23 6:51 i2c: slave support framework improvements Kachalov Anton
2016-07-23 19:51 ` Wolfram Sang
2016-07-25 7:02 ` Kachalov Anton
2016-07-25 7:21 ` Wolfram Sang [this message]
2016-07-25 7:47 ` Kachalov Anton
2016-07-25 8:28 ` Wolfram Sang
2016-07-25 9:11 ` Kachalov Anton
2016-07-25 9:41 ` Wolfram Sang
2016-07-25 10:00 ` Kachalov Anton
2016-07-26 9:50 ` Peter Rosin
2016-07-26 16:51 ` Kachalov Anton
2016-07-28 6:55 ` Peter Rosin
2016-07-28 8:25 ` Peter Rosin
2016-07-28 14:39 ` Kachalov Anton
2016-07-28 7:41 ` Wolfram Sang
2016-07-28 8:20 ` Peter Rosin
2016-07-28 8:39 ` Wolfram Sang
2016-07-28 8:54 ` Peter Rosin
2016-07-28 9:15 ` Wolfram Sang
2016-07-28 9:39 ` Peter Rosin
2016-08-01 10:46 ` Wolfram Sang
2016-08-15 8:58 ` Peter Rosin
2016-08-16 12:12 ` Wolfram Sang
2016-08-16 13:33 ` Peter Rosin
2016-08-16 13:53 ` Kachalov Anton
2016-07-28 14:44 ` Kachalov Anton
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=20160725072151.GA1599@katana \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=mouse@mayc.ru \
/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