All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Stephen Warren <swarren@nvidia.com>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>,
	David Henningsson <david.henningsson@canonical.com>
Subject: Re: [PATCH] ALSA: HDA: Add jack detection for HDMI
Date: Tue, 17 May 2011 18:08:08 +0200	[thread overview]
Message-ID: <s5haael5mzb.wl%tiwai@suse.de> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF04986AAA0D@HQMAIL01.nvidia.com>

At Tue, 17 May 2011 09:00:51 -0700,
Stephen Warren wrote:
> 
> David Henningsson wrote at Tuesday, May 17, 2011 7:47 AM:
> > Just as for headphones and microphone jacks, this patch adds reporting
> > of HDMI jack status through the input layer.
> 
> Interesting. I was asked to look into this, but you beat me to it; thanks!
> 
> A couple questions though:
> 
> a) Is it possible to report more information alongside the plug events,
> such as ELD/EDID content? Or, is the idea that the kernel sends a plug
> event, and then user-space retrieves that information via some other
> API? I don't think there's an API to retrieve ELD information at present
> though right? Although certainly it'd make sense for that to be a 
> completely separate patch.

A simple approach would be adding a control element containing
byte-array of ELD/EDID.

> b) We might discuss how to tie ALSA jacks/ports/PCMs to X displays in
> some way, so that we can represent to the user which specific active
> monitor is the one that supports audio (e.g. in a 2-head setup with both
> monitors connected over HDMI, yet only 1 monitor supports audio).

Yeah, most tight coupling with display vs audio-port is needed.

> I note that the ELD data contains a port_id field, which might be usable
> for this purpose. Could this contain an xrandr value, or an NV-CTRL
> (NVIDIA's proprietary control protocol) display ID, or something similar?

Hm, rather it's a question to X side, i.e. what information is exposed
via xrandr.


Takashi

  reply	other threads:[~2011-05-17 16:08 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 13:46 [PATCH] ALSA: HDA: Add jack detection for HDMI David Henningsson
2011-05-17 15:46 ` Takashi Iwai
2011-05-19  9:55   ` David Henningsson
2011-05-19 10:06     ` Takashi Iwai
2011-05-19 10:24       ` Setting invalid samplerate Torsten Schenk
2011-05-19 10:32         ` Torsten Schenk
2011-05-19 10:55         ` Clemens Ladisch
2011-05-19 11:28           ` Torsten Schenk
2011-05-19 11:36             ` Daniel Mack
2011-05-23 21:49       ` [PATCH] ALSA: HDA: Add jack detection for HDMI Stephen Warren
2011-05-24  5:39         ` Takashi Iwai
2011-05-24 17:27           ` Stephen Warren
2011-05-24 18:09             ` Takashi Iwai
2011-05-24 19:18               ` Stephen Warren
2011-05-24 21:00           ` Stephen Warren
2011-05-19 16:57     ` Stephen Warren
2011-05-19 22:45       ` David Henningsson
2011-05-19 22:51         ` Stephen Warren
2011-06-09 20:59           ` Stephen Warren
2011-05-17 16:00 ` Stephen Warren
2011-05-17 16:08   ` Takashi Iwai [this message]
2011-05-17 17:09     ` pl bossart
2011-05-17 17:31       ` Takashi Iwai
2011-05-17 20:51         ` pl bossart
2011-05-17 21:42           ` Stephen Warren
2011-05-17 22:11             ` pl bossart
2011-05-17 23:14               ` Stephen Warren
2011-05-18 15:43         ` pl bossart
2011-05-18 15:49           ` Takashi Iwai
2011-05-18 10:02 ` Takashi Iwai
2011-05-20 21:59 ` Stephen Warren
2011-05-21  6:25   ` David Henningsson
2011-05-21  7:37     ` Takashi Iwai
2011-05-23 15:29     ` Stephen Warren

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=s5haael5mzb.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=david.henningsson@canonical.com \
    --cc=swarren@nvidia.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.