From: Jens Taprogge <[email protected]> Resetting the previous timeout we avoid to read the timeout status register and see timeout errors that don't correspond to the present state of the device.
Signed-off-by: Jens Taprogge <[email protected]> Signed-off-by: Samuel Iglesias Gonsálvez <[email protected]> --- drivers/staging/ipack/ipack.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/staging/ipack/ipack.c b/drivers/staging/ipack/ipack.c index e2f819c..08b122d 100644 --- a/drivers/staging/ipack/ipack.c +++ b/drivers/staging/ipack/ipack.c @@ -379,6 +379,8 @@ struct ipack_device *ipack_device_register(struct ipack_bus_device *bus, if (bus->ops->set_clockrate(dev, 8)) dev_warn(&dev->dev, "failed to switch to 8 MHz operation for reading of device ID.\n"); + if (bus->ops->reset_timeout(dev)) + dev_warn(&dev->dev, "failed to reset potential timeout."); ret = ipack_device_read_id(dev); if (ret < 0) { -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
