23.01.2019 2:26, Sowjanya Komatineni пишет:
>
>
> + if (i2c_dev->msg_err == I2C_ERR_ARBITRATION_LOST) {
> + if (!i2c_dev->is_multimaster_mode)
> + return tegra_i2c_issue_bus_clear(i2c_dev);
> + return -EAGAIN;
This changes the returned err
В Tue, 22 Jan 2019 23:26:08 +
Sowjanya Komatineni пишет:
> >> >> + if (i2c_dev->msg_err == I2C_ERR_ARBITRATION_LOST) {
> >> >> + if (!i2c_dev->is_multimaster_mode)
> >> >> + return
> >> >> tegra_i2c_issue_bus_clear(i2c_dev);
> >> >> + re
>> >> + if (i2c_dev->msg_err == I2C_ERR_ARBITRATION_LOST) {
>> >> + if (!i2c_dev->is_multimaster_mode)
>> >> + return tegra_i2c_issue_bus_clear(i2c_dev);
>> >> + return -EAGAIN;
>> >
>> >This changes the returned errno from -EIO to -EAGAIN for the
>> >supports_bus
В Tue, 22 Jan 2019 22:13:53 +
Sowjanya Komatineni пишет:
> >> Bus clear feature of tegra i2c controller helps to recover from
> >> bus hang when i2c master loses the bus arbitration due to the
> >> slave device holding SDA LOW continuously for some unknown reasons.
> >>
> >> Per I2C specific
>> Bus clear feature of tegra i2c controller helps to recover from bus
>> hang when i2c master loses the bus arbitration due to the slave device
>> holding SDA LOW continuously for some unknown reasons.
>>
>> Per I2C specification, the device that held the bus LOW should release
>> it within
22.01.2019 23:02, Sowjanya Komatineni пишет:
> Bus clear feature of tegra i2c controller helps to recover from
> bus hang when i2c master loses the bus arbitration due to the
> slave device holding SDA LOW continuously for some unknown reasons.
>
> Per I2C specification, the device that held the b
Bus clear feature of tegra i2c controller helps to recover from
bus hang when i2c master loses the bus arbitration due to the
slave device holding SDA LOW continuously for some unknown reasons.
Per I2C specification, the device that held the bus LOW should
release it within 9 clock pulses.
During
7 matches
Mail list logo
