From: Wolfram Sang <wsa@the-dreams.de>
To: Biju Das <biju.das@bp.renesas.com>
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, linux-renesas-soc@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH 0/2] Use demuxer for i2c1 and i2c5
Date: Mon, 22 Jan 2018 12:40:26 +0100 [thread overview]
Message-ID: <20180122114026.uqozk4cbhfrjwqmd@katana> (raw)
In-Reply-To: <1516620563-7965-1-git-send-email-biju.das@bp.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
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?
I posted and just merged bus recovery to the i2c-rcar driver. Did you
test that? In theory, this should be enough.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-01-22 11:40 UTC|newest]
Thread overview: 10+ 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 ` Wolfram Sang [this message]
2018-01-22 11:55 ` [PATCH 0/2] Use demuxer for i2c1 and i2c5 Biju Das
2018-01-22 12:22 ` Wolfram Sang
2018-01-22 14:03 ` Biju Das
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=20180122114026.uqozk4cbhfrjwqmd@katana \
--to=wsa@the-dreams.de \
--cc=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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.