All of lore.kernel.org
 help / color / mirror / Atom feed
From: "\"David Müller (ELSOFT AG)\"" <d.mueller@elsoft.ch>
To: dri-devel@lists.freedesktop.org
Subject: [i915][855GME][GMBUS] Detection of DVO transmitter unreliable
Date: Tue, 16 Apr 2013 09:53:24 +0200	[thread overview]
Message-ID: <516D0374.3040706@elsoft.ch> (raw)

Hello

I have a 855GME based system with a TFP410 DVO transmitter and running a
vanilla Linux-3.8 kernel.

With the activation of the hardware assisted GMBUS feature (somewhere
near kernel 3.5), the detection of the TFP410 DVO transmitter has become
flacky, which results in an unusable DVO port.

As a first test, i reduced the I2C frequency from 100kHz to 50kHz and
the problem vanished. I used a scope to check the signal quality on the
I2C lines to the DVO transmitter, but everything seems to be within the
specs.

I also checked the whole DVO transmitter initialisation sequence defined
in "intel_dvo.c" and there i noticed that the I2C communication is
completely messed up for 1 or 2 I2C transaction after the receipt of the
first NAK (in my case, this will be for the CH7xxx chip at addr 0x76).

In the "intel_i2c.c" file, there is a remark that one has to be careful
when clearing the NAK condition, otherwise the next I2C transaction may
fail. I played around with this piece of code by adding additional
delays but to no avail so far.

In the same file, there is also a line which disables the hardware
assisted GMBUS functionality for i830 based system.
Does anybody know if the 855GME may be struck by the same problem as the
i830?


Currenty i have figured out two possible work-arounds:
 - add "IS_I85X()" to the list of broken systems
 - reduce the clock rate from 100kHz to 50kHz


Does anybody have an idea what this could be and how to fix it?


Dave

             reply	other threads:[~2013-04-16  8:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16  7:53 "David Müller (ELSOFT AG)" [this message]
2013-04-16 19:10 ` [i915][855GME][GMBUS] Detection of DVO transmitter unreliable 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=516D0374.3040706@elsoft.ch \
    --to=d.mueller@elsoft.ch \
    --cc=dri-devel@lists.freedesktop.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.