On Thu, 2017-03-16 at 17:24 +0100, Oliver Neukum wrote: > Our testing shows the semaphore failing to be transferred on > CherryTrail > in about 0.5% of all cases. The existing timeout needs to be > lengthened > to accomodate the worst cases. I think it's just a semi-hiding of real issue. Hans? > > Signed-off-by: Oliver Neukum <oneukum@xxxxxxxx> > --- > drivers/i2c/busses/i2c-designware-baytrail.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/i2c/busses/i2c-designware-baytrail.c > b/drivers/i2c/busses/i2c-designware-baytrail.c > index 1590ad0..2d238e3 100644 > --- a/drivers/i2c/busses/i2c-designware-baytrail.c > +++ b/drivers/i2c/busses/i2c-designware-baytrail.c > @@ -21,7 +21,7 @@ > > #include "i2c-designware-core.h" > > -#define SEMAPHORE_TIMEOUT 100 > +#define SEMAPHORE_TIMEOUT 500 > #define PUNIT_SEMAPHORE 0x7 > #define PUNIT_SEMAPHORE_BIT BIT(0) > #define PUNIT_SEMAPHORE_ACQUIRE BIT(1) -- Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> Intel Finland Oy -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
