Em Sun, 12 Jan 2014 16:29:26 +0100
Frank Schäfer escreveu:
> On 11.01.2014 21:27, Mauro Carvalho Chehab wrote:
> > Em Sat, 11 Jan 2014 14:14:38 +0100
> > Frank Schäfer escreveu:
> >
> >> Am 10.01.2014 09:33, schrieb Mauro Carvalho Chehab:
> >>> If i2c_debug is enabled, we splicitly want to know
On 11.01.2014 21:27, Mauro Carvalho Chehab wrote:
Em Sat, 11 Jan 2014 14:14:38 +0100
Frank Schäfer escreveu:
Am 10.01.2014 09:33, schrieb Mauro Carvalho Chehab:
If i2c_debug is enabled, we splicitly want to know when a
device fails with timeout.
If i2c_debug==2, this is already provided, for
Em Sat, 11 Jan 2014 14:14:38 +0100
Frank Schäfer escreveu:
> Am 10.01.2014 09:33, schrieb Mauro Carvalho Chehab:
> > If i2c_debug is enabled, we splicitly want to know when a
> > device fails with timeout.
> >
> > If i2c_debug==2, this is already provided, for each I2C transfer
> > that fails.
>
Am 10.01.2014 09:33, schrieb Mauro Carvalho Chehab:
> If i2c_debug is enabled, we splicitly want to know when a
> device fails with timeout.
>
> If i2c_debug==2, this is already provided, for each I2C transfer
> that fails.
>
> However, most of the time, we don't need to go that far. We just
> want
If i2c_debug is enabled, we splicitly want to know when a
device fails with timeout.
If i2c_debug==2, this is already provided, for each I2C transfer
that fails.
However, most of the time, we don't need to go that far. We just
want to know that I2C transfers fail.
So, add such errors for normal
