public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915/crt: Remove 0xa0 probe for CRT
Date: Mon, 04 Apr 2011 09:26:20 -0700	[thread overview]
Message-ID: <yun7hbaaspf.fsf@aiko.keithp.com> (raw)
In-Reply-To: <849307$cab831@azsmga001.ch.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 1353 bytes --]

On Mon, 04 Apr 2011 16:29:55 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:

> Yes. I'm saying that that the controller accepts a write to port 0xa0.

So it's the GMBUS controller itself then, I guess. Weird.

Let me see if I understand how it used to work and why fixing the GMBUS
reset causes it to break in this case.

In the distant past (pre-GMBUS)

 1) Some previous DDC transaction would fail, but without GMBUS
    this would not break the bus
 2) The 0xA0 transaction would fail as there wasn't anyone
    listening on the DDC bus.
 3) The 0x50 transaction would also fail, again because no-one
    was listening
 4) The monitor would be reported as disconnected.

In the recent past (post-GMBUS):

 1) Some previous DDC transaction would fail, wedging the GMBUS
 2) The 0xA0 transaction would then fail due to the GMBUS breakage
 3) The 0x50 transaction would also fail as the GMBUS was wedged
 4) The VGA port would be reported as disconnected

With the GMBUS reset:

 1) Some previous DDC transaction would fail, but the GMBUS would get
    reset
 2) The 0xA0 transaction would now succeed.
 3) The VGA port would be reported as connected.

Do we have any idea what ports the GMBUS controller is listening
internally for? And, whether this differs from chip to chip?

-- 
keith.packard@intel.com

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2011-04-04 16:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  6:26 [PATCH 1/2] drm/i915/crt: Remove 0xa0 probe for CRT Chris Wilson
2011-04-04  6:26 ` [PATCH 2/2] drm/i915/crt: Explicitly return false if connected to a digital monitor Chris Wilson
2011-04-04 15:09   ` Keith Packard
2011-04-04 15:25     ` Chris Wilson
2011-04-04 16:27       ` Keith Packard
2011-04-04 15:08 ` [PATCH 1/2] drm/i915/crt: Remove 0xa0 probe for CRT Keith Packard
2011-04-04 15:29   ` Chris Wilson
2011-04-04 16:26     ` Keith Packard [this message]
2011-04-05  0:19       ` Dave Airlie
2011-04-05  1:04         ` Keith Packard
2011-04-05  9:18       ` Chris Wilson
2011-04-05  1:57 ` Keith Packard

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=yun7hbaaspf.fsf@aiko.keithp.com \
    --to=keithp@keithp.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox