Hi,
> Subject: Re: [PATCH 0/2] Use demuxer for i2c1 and i2c5
>
>
> > > > On top of renesas-dev branch, I am using the below i2c-rcar driver
> > > > related
> > > patches.
> > > >
> > > > https://www.mail-archive.com
> > > On top of renesas-dev branch, I am using the below i2c-rcar driver related
> > patches.
> > >
> > > https://www.mail-archive.com/linux-renesas-soc@vger.kernel.org/msg2227
> > > 8.html
> >
> > Those should be enough. They are not?
>
> Yes. I have tested without demuxer patches, I confirm,
> Subject: Re: [PATCH 0/2] Use demuxer for i2c1 and i2c5
[>]
> > How do i2c-bus gets details of gpio lines associated with i2c bus for bus
> recovery?
>
> As you can see in the code, you don't need GPIOs if you can control SDA and
> SCL
> directly. The I2C IP ca
> How do i2c-bus gets details of gpio lines associated with i2c bus for bus
> recovery?
As you can see in the code, you don't need GPIOs if you can control SDA
and SCL directly. The I2C IP can do this.
> On top of renesas-dev branch, I am using the below i2c-rcar driver related
> patches.
>
> Subject: Re: [PATCH 0/2] Use demuxer for i2c1 and i2c5
>
> On Mon, Jan 22, 2018 at 11:29:21AM +, Biju Das wrote:
> > We have observed that on iWave RZ/G1E boards, randomly HDMI slave
> > device is holding data line after a soft reboot.
> >
> > We applied
On Mon, Jan 22, 2018 at 11:29:21AM +, Biju Das wrote:
> We have observed that on iWave RZ/G1E boards, randomly HDMI slave device
> is holding data line after a soft reboot.
>
> We applied demuxer patch for i2c1 and using an oscilloscope verified that
> i2c recovery works on the failure
