Sorry for late reply.
Bad UA configuration. Will resend straight away.
Thanks,
Josef
On Thu, 25 Apr 2013, Wolfram Sang wrote:
Still can't apply :( Whitespace problems in the patch context :(
--
To unsubscribe from this list: send the line unsubscribe linux-i2c in
the body of a message to
From 8a4773d0c0df6fe2e816ad37fde30a2d90a1ad31 Mon Sep 17 00:00:00 2001
From: Josef Ahmad josef.ah...@linux.intel.com
Date: Fri, 19 Apr 2013 17:28:10 +0100
Subject: [PATCH] i2c-designware: fix RX FIFO overrun
i2c_dw_xfer_msg() pushes a number of bytes to transmit/receive
to/from the bus into the
Hi all,
I've read the discussion on multimaster and I have to agree with Uwe about
masters doing the arbitration (and retry). However, there's another issue which
one quickly discovers when adding a second master on a physical i2c bus.
Here's the scenario: Using driver jc42 which adds a detect
On Wed, May 08, 2013 at 11:57:59AM -0400, Jean-François Dagenais wrote:
Hi all,
I've read the discussion on multimaster and I have to agree with Uwe about
masters doing the arbitration (and retry). However, there's another issue
which one quickly discovers when adding a second master on a
On 2013-05-08, at 13:54, Guenter Roeck wrote:
[...]
Isn't it the point of having multiple masters on the same bus, that each of
them can manage the same devices ?
I wouldn't think so. You mention why in your last paragraph and I totally see
and agree with that. So that is not my intention at
On Wed, May 08, 2013 at 09:50:44PM -0400, Jean-François Dagenais wrote:
On 2013-05-08, at 13:54, Guenter Roeck wrote:
[...]
Isn't it the point of having multiple masters on the same bus, that each of
them can manage the same devices ?
I wouldn't think so. You mention why in your last
