dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Keith Packard <keithp@keithp.com>, Jerome Glisse <jglisse@redhat.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/radeon/kms: Use the standard VESA timeout for DDC channels
Date: Wed, 21 Mar 2012 13:22:22 +0100	[thread overview]
Message-ID: <201203211322.22325.jdelvare@suse.de> (raw)
In-Reply-To: <86pqe3qoky.fsf@sumi.keithp.com>

Hi Keith,

On Sunday 29 January 2012 02:34:05 am Keith Packard wrote:
> On Sat, 28 Jan 2012 11:08:58 +0100, Jean Delvare <jdelvare@suse.de>
> wrote:
> > The VESA specification suggests a 2.2 ms timeout on DDC channels.
> > Use exactly that (as the i915 driver does) instead of hard-coding a
> > jiffy count.
> 
> The Vesa spec seems to say 2ms; at least according to the DDC/CI spec
> paragraph 6.6.

To be honest, I did not read it, I don't even think it is publicly 
available, is it? I did naively trust the comment in radeon_i2c.c: "vesa 
says 2.2 ms is enough". Not sure where this value came from if you claim 
the spec says 2 ms. Jerome, you wrote this comment in the first place, 
want to comment on that?

The Intel drivers are using 2.2 ms too, since November 2008 (added to 
i915 driver by Jesse Barnes.) Maybe this all originates from X11 driver 
code?

> usecs_to_jiffies rounds the value it gets up, so we
> should never get an interval less than 2ms if we pass 2000us to it.

Technically I agree, all we need to agree on is the value, 2000 us or 
2200 us. I don't mind either way, I am not aware of specific complaints 
about the current code, I was just trying to clean things up, as hard-
coding jiffy counts is bad and having different timeouts in the various 
drivers makes little sense IMHO.

-- 
Jean Delvare
Suse L3

      reply	other threads:[~2012-03-21 12:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-28 10:08 [PATCH 2/2] drm/radeon/kms: Use the standard VESA timeout for DDC channels Jean Delvare
2012-01-28 14:46 ` Alex Deucher
2012-01-29  1:34 ` Keith Packard
2012-03-21 12:22   ` Jean Delvare [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=201203211322.22325.jdelvare@suse.de \
    --to=jdelvare@suse.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jglisse@redhat.com \
    --cc=keithp@keithp.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