From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: Doug Anderson <dianders@chromium.org>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Andy Yan <andy.yan@rock-chips.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4] drm: bridge/dw_hdmi: add dw hdmi i2c bus adapter support
Date: Mon, 28 Sep 2015 22:59:00 +0300 [thread overview]
Message-ID: <56099C04.9050201@mentor.com> (raw)
In-Reply-To: <CAD=FV=W6h6Nd=HQPYDcarCVNBmDQ6k4P2=Y_9rn6WM9Zc5ammw@mail.gmail.com>
Hi Doug,
On 28.09.2015 19:29, Doug Anderson wrote:
> Vladimir,
>
> On Mon, Sep 21, 2015 at 8:07 AM, Vladimir Zapolskiy
> <vladimir_zapolskiy@mentor.com> wrote:
>> - do I2C bus controller reinitialization on every data transfer,
>> this change hopefully solves some observed problems on RK3288 platform
>
> My apologies, but this appears to be a bad idea...
>
> We just discovered that this was the root cause of a bug. If an HDCP
> transfer is happening then the soft reset messes things up. In our
> tree we've moving things back to the way they were. :(
therefore I do the same.
Since unfortunately I'm limited in testing your tree and RK3288
platform, probably it might be more productive, if you send any updates
on top of my changes -- I'll be capable to review/test them for
regressions on iMX6 in vanilla.
--
With best wishes,
Vladimir
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-09-28 19:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 15:07 [PATCH v4] drm: bridge/dw_hdmi: add dw hdmi i2c bus adapter support Vladimir Zapolskiy
2015-09-28 16:29 ` Doug Anderson
2015-09-28 19:59 ` Vladimir Zapolskiy [this message]
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=56099C04.9050201@mentor.com \
--to=vladimir_zapolskiy@mentor.com \
--cc=andy.yan@rock-chips.com \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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