From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] i2c: Providing hooks for i2c multimaster bus arbitration.
Date: Tue, 12 Feb 2013 10:49:29 +0000 [thread overview]
Message-ID: <511A1E39.5000304@codethink.co.uk> (raw)
In-Reply-To: <20130210181710.GB12760@nekote.pengutronix.de>
On 10/02/13 18:17, Wolfram Sang wrote:
> On Mon, Feb 04, 2013 at 02:33:15PM +0530, Yuvaraj Kumar C D wrote:
>> This RFC patch is w.r.t multimaster bus arbitration which is already
>> being discussing in the mainline.
>> This patch provides hooks for the i2c multimaster bus arbitration
>> and to have the arbitration parameters.
>
> I still haven't understood why the arbitration specified in the I2C
> standard is not enough for you. Or what you would need to make use of
> it.
I am a little concerned as there is no way to actually lock a bus to
stop another master from transmitting. You can get collisions in a
multi-master environment. Drivers need fixing to deal with collisions
and let the sender know the operation has failed.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2013-02-12 10:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 9:03 [RFC] i2c: Providing hooks for i2c multimaster bus arbitration Yuvaraj Kumar C D
2013-02-04 11:13 ` Yuvaraj Kumar
2013-02-06 0:23 ` Doug Anderson
[not found] ` <CAD=FV=VQywwQ3YAFb=1qFmd3UEW39Xu=ok6fdjhvBXdwOQOa1Q@mail.gmail.com>
2013-02-06 5:28 ` Yuvaraj Kumar
2013-02-06 5:33 ` Yuvaraj Kumar
2013-02-06 6:00 ` Simon Glass
2013-02-10 18:17 ` Wolfram Sang
2013-02-11 23:53 ` Doug Anderson
2013-02-12 0:17 ` Simon Glass
2013-02-12 10:03 ` Wolfram Sang
2013-02-12 10:49 ` Ben Dooks [this message]
2013-02-12 16:48 ` Uwe Kleine-König
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=511A1E39.5000304@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).