From: Wolfram Sang <wsa@the-dreams.de>
To: Peter Rosin <peda@axentia.se>
Cc: Kachalov Anton <mouse@mayc.ru>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: Re: i2c: slave support framework improvements
Date: Thu, 28 Jul 2016 10:39:14 +0200 [thread overview]
Message-ID: <20160728083914.GC2693@katana> (raw)
In-Reply-To: <9bf9e528-de4a-df4d-fed4-ee1afbfb609a@axentia.se>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
> In proximity to this, I find it odd that you are allowed to register
> a slave device with the same address as a client device on an adapter
> (one has I2C_CLIENT_FLAG set, which sets I2C_ADDR_OFFSET_SLAVE before
> the address comparisons). Why is that possible? Yes, the two devices
> can probably talk each other, both being aware of who is master at
> the moment, but what about other masters on the bus?
Just a quick answer to this first: The Tegra community wanted to have
loopback support. According to documentation, their hardware can indeed
read from their own slave device. So, we needed this distinction to
instantiate the slave backend driver and the regular driver.
I don't understand the multi-master question: The I2C slave device
should react to any bus master anyhow. And for competing bus masters,
there is the arbitration mechanism.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-28 8:39 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
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 [this message]
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=20160728083914.GC2693@katana \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=mouse@mayc.ru \
--cc=peda@axentia.se \
/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;
as well as URLs for NNTP newsgroup(s).