All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>,
	alsa-devel@alsa-project.org, fengguang.wu@intel.com,
	pierre-louis.bossart@linux.intel.com,
	Wang Xingchao <xingchao.wang@intel.com>
Subject: Re: [PATCH 0/3] Make HDMI ELD usable with hotplug
Date: Tue, 19 Feb 2013 06:55:36 +0100	[thread overview]
Message-ID: <512313D8.901@canonical.com> (raw)
In-Reply-To: <20130218223942.GB3605@sci.fi>

On 02/18/2013 11:39 PM, Ville Syrjälä wrote:
> On Mon, Feb 18, 2013 at 02:50:49PM +0100, David Henningsson wrote:
>> On 02/18/2013 02:35 PM, Takashi Iwai wrote:
>>> At Mon, 18 Feb 2013 14:11:10 +0100,
>>> David Henningsson wrote:
>>>>
>>>> I'm experimenting with using ELD information in PulseAudio and found
>>>> that it didn't work very well with hotplugging.
>>>> Neither the proc file nor the ELD kcontrol was cleared correctly after
>>>> unplug, and there was no way (except polling) to find out when ELD
>>>> has become available.
>>>
>>> Did you try Xingchao's patch for drm/i915?  It's queued in
>>> drm-intel-next:
>>>
>>>       commit 7b9f35a6dd72f89452c58bbdbaf063027bf857ec
>>>       Author: Wang Xingchao <xingchao.wang@intel.com>
>>>       Date:   Tue Jan 22 23:25:25 2013 +0800
>>>
>>>       drm/i915: HDMI/DP - ELD info refresh support for Haswell
>>
>> Thanks for the hint. I'm currently developing not on a Haswell machine,
>> but an (I think) Arrandale that I bought a few years ago. So I guess
>> this patch does not have any effect on my hw?
>
> While reviewing that patch I asked whether we need something like that
> on other platforms. Unfortunately I didn't get a real answer. The logic
> in the patch would seem to apply equally to all platforms, not just HSW.
> We also seem to be doing silly things like flipping the ELD valid bit
> in the register on and off a few times when we update the ELD. But I'm
> not all that familiar with the topic so take my ramblings with a pinch
> of salt.
>
> But in any case, if you're seeing a problem with the behaviour of i915
> you should definitely report it.

Looking at the HDA spec [1], e g "Figure 72: PD and ELDV unsolicited 
responses flow for digital display codecs" it looks like it's not valid 
to first send the PD bit and then ELDV a while later. So then I guess 
it's an issue that this actually seem to happen on the machine I use for 
testing this code.

 From the same figure, it also looks like ELDV can be flipped back and 
forth (due to mode changes) when PD is true; so making patches that deal 
with PD and ELDV independently seem to be the right thing nonetheless.


-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

[1] 
http://www.intel.com/content/www/us/en/standards/high-definition-audio-specification.html

      parent reply	other threads:[~2013-02-19  5:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 13:11 [PATCH 0/3] Make HDMI ELD usable with hotplug David Henningsson
2013-02-18 13:11 ` [PATCH 1/3] ALSA: hda - hdmi: ELD shouldn't be valid after unplug David Henningsson
2013-02-18 13:11 ` [PATCH 2/3] ALSA: hda - hdmi: Do not expose eld data when eld is invalid David Henningsson
2013-02-18 14:39   ` Takashi Iwai
2013-02-18 13:11 ` [PATCH 3/3] ALSA: hda - hdmi: Notify userspace when ELD control changes David Henningsson
2013-02-18 14:41   ` Takashi Iwai
2013-02-18 14:46     ` David Henningsson
2013-02-18 14:55       ` Takashi Iwai
2013-02-18 15:09         ` David Henningsson
2013-02-18 15:14           ` Takashi Iwai
2013-02-18 16:08             ` David Henningsson
2013-02-18 16:21               ` Takashi Iwai
2013-02-18 13:35 ` [PATCH 0/3] Make HDMI ELD usable with hotplug Takashi Iwai
2013-02-18 13:50   ` David Henningsson
2013-02-18 14:28     ` Takashi Iwai
2013-02-18 14:33       ` Takashi Iwai
2013-02-18 22:39     ` Ville Syrjälä
2013-02-19  2:39       ` Wang xingchao
2013-02-19  5:55       ` David Henningsson [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=512313D8.901@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=fengguang.wu@intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.de \
    --cc=xingchao.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.