public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Jackson <ajax@redhat.com>
To: Andy Lutomirski <luto@mit.edu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] Intel graphics CPU usage - SDVO detect bogosity?
Date: Mon, 16 Aug 2010 11:13:51 -0400	[thread overview]
Message-ID: <1281971631.17843.12721.camel@atropine> (raw)
In-Reply-To: <4C694ABF.6020505@mit.edu>

[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]

On Mon, 2010-08-16 at 10:27 -0400, Andy Lutomirski wrote:

> But that's really the problem, because intel_sdvo_dvi_init contains:
> 
>          connector->polled = DRM_CONNECTOR_POLL_CONNECT | DRM_CONNECTOR_POLL_DISCONNECT;
> 
> I don't know if SDVO is supposed to send hotplug interrupts because
> that section of the docs is incomplete.

SDVO can generate interrupts, although a particular SDVO output type
might not.  (The G45 docs are missing this section, but the 965 docs are
applicable.)  We don't have that turned on, of course, because that
would be entirely too sensible.

You'd probably need to uncomment the #if 0'd intel_sdvo_set_hotplug() in
intel_sdvo.c, and call that from the appropriate bit of
intel_sdvo_init().  For pre-gen4 you'd probably also need to set
SDVO_INTERRUPT_ENABLE in the appropriate SDVOx register, but in gen4+
that bit is used for bpc selection.

Having done that you'd then need to wait the inevitable six months to
find out which SDVO devices actually have functioning hotplug and which
ones are just plain lying about it.

- ajax

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-08-16 15:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-16  2:32 Intel graphics CPU usage - SDVO detect bogosity? Linus Torvalds
2010-08-16  2:51 ` Markus Trippelsdorf
2010-08-16  3:30 ` Dave Airlie
2010-08-16  4:01   ` Linus Torvalds
2010-08-16  4:29     ` Dave Airlie
2010-08-16  4:06 ` Andy Lutomirski
2010-08-16  4:27   ` Linus Torvalds
2010-08-16 14:27     ` Andy Lutomirski
2010-08-16 15:13       ` Adam Jackson [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=1281971631.17843.12721.camel@atropine \
    --to=ajax@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@mit.edu \
    --cc=torvalds@linux-foundation.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