From: Biju Das <biju.das@bp.renesas.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Chris Paterson <Chris.Paterson2@renesas.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Subject: RE: [PATCH 0/2] Use demuxer for i2c1 and i2c5
Date: Mon, 22 Jan 2018 11:55:54 +0000 [thread overview]
Message-ID: <KL1PR06MB170270EA30591C7636941361B8EC0@KL1PR06MB1702.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <20180122114026.uqozk4cbhfrjwqmd@katana>
> Subject: Re: [PATCH 0/2] Use demuxer for i2c1 and i2c5
>
> On Mon, Jan 22, 2018 at 11:29:21AM +0000, 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 condition.
>
> Do you really need the demuxer for that?
How do i2c-bus gets details of gpio lines associated with i2c bus for bus recovery?
For eg:- i2c1 scl line --> gpio0 11
I2c1 sda line --> gpio0 12
> I posted and just merged bus recovery to the i2c-rcar driver. Did you test that?
> In theory, this should be enough.
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/msg22278.html
Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.
next prev parent reply other threads:[~2018-01-22 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 11:29 [PATCH 0/2] Use demuxer for i2c1 and i2c5 Biju Das
2018-01-22 11:29 ` [PATCH vY 1/2] ARM: dts: iwg22d-sodimm-dbhd-ca: use demuxer for I2C1 Biju Das
2018-01-22 11:29 ` [PATCH vY 2/2] ARM: dts: iwg22d-sodimm: use demuxer for I2C5 Biju Das
2018-01-22 11:40 ` [PATCH 0/2] Use demuxer for i2c1 and i2c5 Wolfram Sang
2018-01-22 11:55 ` Biju Das [this message]
2018-01-22 12:22 ` Wolfram Sang
2018-01-22 14:03 ` Biju Das
2018-01-22 14:08 ` Wolfram Sang
2018-01-23 13:39 ` Biju Das
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=KL1PR06MB170270EA30591C7636941361B8EC0@KL1PR06MB1702.apcprd06.prod.outlook.com \
--to=biju.das@bp.renesas.com \
--cc=Chris.Paterson2@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=horms@verge.net.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).