Regards
Shashank
On 8/24/2017 5:49 PM, Imre Deak wrote:
On Thu, Aug 24, 2017 at 05:40:32PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 8/24/2017 5:19 PM, Imre Deak wrote:
On Wed, Aug 23, 2017 at 06:12:51PM +0530, Shashank Sharma wrote:
From the CI builds, its been observed that
On Thu, Aug 24, 2017 at 05:40:32PM +0530, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 8/24/2017 5:19 PM, Imre Deak wrote:
> > On Wed, Aug 23, 2017 at 06:12:51PM +0530, Shashank Sharma wrote:
> > > From the CI builds, its been observed that during a driver
> > > reload/insert, dp dua
Regards
Shashank
On 8/24/2017 5:19 PM, Imre Deak wrote:
On Wed, Aug 23, 2017 at 06:12:51PM +0530, Shashank Sharma wrote:
From the CI builds, its been observed that during a driver
reload/insert, dp dual mode read function sometimes fails to
read from dual mode devices (like LSPCON) over i2c-
On Wed, Aug 23, 2017 at 06:12:51PM +0530, Shashank Sharma wrote:
> From the CI builds, its been observed that during a driver
> reload/insert, dp dual mode read function sometimes fails to
> read from dual mode devices (like LSPCON) over i2c-over-aux
> channel.
>
> This patch:
> - adds some delay
From the CI builds, its been observed that during a driver
reload/insert, dp dual mode read function sometimes fails to
read from dual mode devices (like LSPCON) over i2c-over-aux
channel.
This patch:
- adds some delay and few retries, allowing a scope for these
devices to settle down and respon
