From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
Cc: Thierry Reding <treding@nvidia.com>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/dp: Use large transactions for I2C over AUX
Date: Fri, 23 Jan 2015 21:46:29 +0200 [thread overview]
Message-ID: <20150123194629.GY19354@intel.com> (raw)
In-Reply-To: <1422038438-9323-1-git-send-email-simon.farnsworth@onelan.co.uk>
On Fri, Jan 23, 2015 at 06:40:38PM +0000, Simon Farnsworth wrote:
> DisplayPort to DVI-D Dual Link adapters designed by Bizlink have bugs in
> their I2C over AUX implementation. They work fine with Windows, but fail
> with Linux.
>
> It turns out that they cannot keep an I2C transaction open unless the
> previous read was 16 bytes; shorter reads can only be followed by a zero
> byte transfer ending the I2C transaction.
>
> Copy Windows's behaviour, and read 16 bytes at a time. Analysis of the
> failure state was provided by Datapath Ltd.
>
> Signed-off-by: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
> ---
> Thierry,
>
> You put in the comment about "decreased performance", back in December 2013;
> would you mind testing that this still works with the devices you tested?
>
> Unfortunately, Bizlink are the only game in town for DP->DVI-DL adapters -
> and their firmware is prone to giving up on I2C if we look at it
> wrongly. Even Apple's device is Bizlink designed.
>
> drivers/gpu/drm/drm_dp_helper.c | 13 +++++--------
> 1 file changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_dp_helper.c b/drivers/gpu/drm/drm_dp_helper.c
> index 79968e3..b4a9d4a 100644
> --- a/drivers/gpu/drm/drm_dp_helper.c
> +++ b/drivers/gpu/drm/drm_dp_helper.c
> @@ -507,16 +507,13 @@ static int drm_dp_i2c_xfer(struct i2c_adapter *adapter, struct i2c_msg *msgs,
> err = drm_dp_i2c_do_msg(aux, &msg);
> if (err < 0)
> break;
> - /*
> - * Many hardware implementations support FIFOs larger than a
> - * single byte, but it has been empirically determined that
> - * transferring data in larger chunks can actually lead to
> - * decreased performance. Therefore each message is simply
> - * transferred byte-by-byte.
> + /* Bizlink designed DP->DVI-D Dual Link adapters require the
> + * I2C over AUX packets to be as large as possible. If not,
> + * the I2C transactions never succeed.
> */
> - for (j = 0; j < msgs[i].len; j++) {
> + for (j = 0; j < msgs[i].len; j+=16) {
> msg.buffer = msgs[i].buf + j;
> - msg.size = 1;
> + msg.size = min(16, msgs[i].len - 16);
I don't think it's quite this simple. The sink is allowed to ACK
partial data for multi-byte messages. The code doesn't handle that.
>
> err = drm_dp_i2c_do_msg(aux, &msg);
> if (err < 0)
> --
> 2.1.0
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-01-23 19:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 18:40 [PATCH] drm/dp: Use large transactions for I2C over AUX Simon Farnsworth
2015-01-23 19:46 ` Ville Syrjälä [this message]
2015-01-23 21:21 ` Thierry Reding
2015-01-24 11:27 ` Daniel Vetter
2015-01-26 9:50 ` Simon Farnsworth
-- strict thread matches above, loose matches on Subject: below --
2015-01-26 15:22 Simon Farnsworth
2015-01-26 15:33 ` Ville Syrjälä
2015-01-26 15:47 ` Simon Farnsworth
2015-01-26 16:11 ` Ville Syrjälä
2015-01-26 16:39 ` Simon Farnsworth
2015-01-27 13:36 ` Ville Syrjälä
2015-01-28 8:59 ` Jani Nikula
2015-01-28 9:10 ` Daniel Vetter
2015-01-28 9:33 ` Jani Nikula
2015-01-28 10:30 ` Daniel Vetter
2015-01-28 10:45 ` Simon Farnsworth
2015-01-26 16:00 ` Ville Syrjälä
2015-02-10 18:38 Simon Farnsworth
2015-02-10 18:42 ` Simon Farnsworth
2015-02-11 5:36 ` Dave Airlie
2015-02-11 7:25 ` Daniel Vetter
2015-02-11 8:13 ` Jani Nikula
2015-02-11 12:05 ` Ville Syrjälä
2015-03-11 19:28 ` Ville Syrjälä
2015-03-11 21:06 ` Daniel Vetter
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=20150123194629.GY19354@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=simon.farnsworth@onelan.co.uk \
--cc=treding@nvidia.com \
/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