From: David Henningsson <david.henningsson@canonical.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: Takashi Iwai <tiwai@suse.de>,
ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ALSA: HDA: Add jack detection for HDMI
Date: Sat, 21 May 2011 08:25:57 +0200 [thread overview]
Message-ID: <4DD75AF5.60209@canonical.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF0498A47E59@HQMAIL01.nvidia.com>
On 2011-05-20 23:59, 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.
>>
>> I considered making additional SND_JACK_* constants for HDMI and
>> Displayport instead of going with SND_JACK_VIDEOOUT, but it didn't seem
>> worth the additions, and breakage of compiling with old kernels, etc.
>> Let me know if you think otherwise and I'll prepare a second patch for
>> that.
>
> One more thought on this:
>
> Some of our older HW (MCP6x, MCP7x chipsets) doesn't support unsolicited
> responses, nor PD/ELDV/ELD data. If PulseAudio is updated to listen to
> these new jack events on kernels where the input files are present,
> that'll presumably cause it never to allow use of the HDMI sinks on those
> chipsets. I don't know if other vendors have this issue or not.
>
> In that case, can we do one of:
>
> * Not create the jack/input files at all.
>
> * Immediately mark the jack as "present".
>
> I assume the latter would be easier for user-space to deal with; it'd be
> more in line with the kernel abstracting HW differences.
>
Ok, thanks for the input (no pun intended ;-) ). If they support
presence detect, we could create a polling loop. Otherwise, don't create
the jack.
Is this autodetectable or do we have to quirk it?
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2011-05-21 6:26 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
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 [this message]
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=4DD75AF5.60209@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=swarren@nvidia.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).