All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: Wu Fengguang <fengguang.wu@intel.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Wang, Zhenyu Z" <zhenyu.z.wang@intel.com>,
	"intel-gfx@lists.freedesktop..."
	<intel-gfx@lists.freedesktop.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	Ben Skeggs <bskeggs@redhat.com>,
	Christopher White <c.white@pulseforce.com>,
	Jeremy Bush <contractfrombelow@gmail.com>,
	"Bossart, Pierre-louis" <pierre-louis.bossart@intel.com>
Subject: Re: [PATCH v3] pass ELD to HDMI/DP audio driver
Date: Wed, 03 Aug 2011 19:48:08 -0700	[thread overview]
Message-ID: <yunk4atlwnr.fsf@aiko.keithp.com> (raw)
In-Reply-To: <20110801135140.GA24205@localhost>


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

On Mon, 1 Aug 2011 21:51:40 +0800, Wu Fengguang <fengguang.wu@intel.com> wrote:

> 1) intel_write_eld() is not called at all
>    It seems we need to call intel_write_eld() in other places besides
>    inside ->mode_set(). Is ->detect() the right place to do so? In
>    other words, are there established connector<=>encoder mapping
>    that can be queried inside intel_hdmi_detect()/intel_dp_detect()?

The connector has a link to the encoder (struct intel_connector contains a
pointer to a struct intel_encoder).

> 2) intel_dp_detect() is called even though it's an HDMI monitor
>    connected to an HDMI jack.. It may be a bug specific to the
>    hardware I'm testing (attached its full dmesg).

We run all of the hotplug functions when any connector change is
detected; easier than trying to track what happened from the bits
visible from the interrupt.

I note that this patch does not include the necessary hooks for
Ivybridge; we'll need that included (and tested) for this to be
considered for kernel 3.1. I'd be surprised if it couldn't use
ironlake_write_eld just fine, so it should just be a matter of setting
the write_eld field and testing it on actual hardware.

-- 
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-08-04  2:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29  6:20 [PATCH] pass ELD to HDMI/DP audio driver Wu Fengguang
2011-06-29  6:36 ` Wu Fengguang
2011-06-29  7:00 ` Takashi Iwai
2011-06-29 13:10 ` [PATCH v2] " Wu Fengguang
2011-06-29 23:11   ` Ben Skeggs
2011-07-29 20:07   ` Jesse Barnes
2011-08-01 13:51     ` [PATCH v3] " Wu Fengguang
2011-08-04  2:48       ` Keith Packard [this message]
2011-08-04  9:40         ` Wu Fengguang
2011-08-04 18:03           ` Keith Packard
2011-08-05 12:49             ` Wu Fengguang
2011-08-05 15:52               ` Stephen Warren
2011-08-06 20:02               ` 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=yunk4atlwnr.fsf@aiko.keithp.com \
    --to=keithp@keithp.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bskeggs@redhat.com \
    --cc=c.white@pulseforce.com \
    --cc=contractfrombelow@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fengguang.wu@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=pierre-louis.bossart@intel.com \
    --cc=zhenyu.z.wang@intel.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 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.