On 03/09/2014 09:28 PM, Wolfram Sang wrote:
On Fri, Feb 28, 2014 at 11:32:05AM +0100, mike.looijm...@topic.nl wrote:
From: Mike Looijmans milo-softw...@users.sourceforge.net
Having a board where the I2C bus locks up occasionally made it clear
that the bus recovery in the i2c-davinci driver
--On March 07, 2014 20:15 +0530 Mugunthan V N mugunthan...@ti.com wrote:
On Friday 07 March 2014 07:37 PM, Christian Riesch wrote:
Signed-off-by: Christian Riesch christian.rie...@omicron.at
Cc: Prabhakar Lad prabhakar.cse...@gmail.com
Cc: Mugunthan V N mugunthan...@ti.com
Cc: Florian
Hi Alexander,
--On March 09, 2014 20:58 +0100 Alexander Holler hol...@ahsoftware.de
wrote:
Hello,
may I ask what's the deal with drivers/usb/musb/davinci.c and why it
depends on BROKEN?
I've just enabled it here and it compiles and seems to work.
I noticed the same for
I won't be doing those changes though. My sponsor's budget is
limited, so I'm just having to do the minimum I can get away with.
Pity. Are you available for testing in case someone comes up with a
patch?
signature.asc
Description: Digital signature
On 03/10/2014 08:26 AM, Wolfram Sang wrote:
I won't be doing those changes though. My sponsor's budget is
limited, so I'm just having to do the minimum I can get away with.
Pity. Are you available for testing in case someone comes up with a
patch?
Not really, the customer is using a
Even more, you should complete the whole transfer. There are devices
where things can really go wrong if you send a half-complete command and
then start with the next one. So, not checking signals at all is the way
to go for I2C drivers. There is some cruft left, so I am happy about
patches
Am 10.03.2014 08:21, schrieb Christian Riesch:
Hi Alexander,
--On March 09, 2014 20:58 +0100 Alexander Holler hol...@ahsoftware.de
wrote:
Hello,
may I ask what's the deal with drivers/usb/musb/davinci.c and why it
depends on BROKEN?
I've just enabled it here and it compiles and seems to
Even more, you should complete the whole transfer. There are devices
where things can really go wrong if you send a half-complete command and
then start with the next one. So, not checking signals at all is the way
to go for I2C drivers. There is some cruft left, so I am happy about
