From: pl bossart <bossart.nospam@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>,
Stephen Warren <swarren@nvidia.com>,
David Henningsson <david.henningsson@canonical.com>
Subject: Re: [PATCH] ALSA: HDA: Add jack detection for HDMI
Date: Wed, 18 May 2011 10:43:36 -0500 [thread overview]
Message-ID: <BANLkTi=oR9VoW8TbgicF0Zg3bSS46kwbkA@mail.gmail.com> (raw)
In-Reply-To: <s5hpqnh2pyu.wl%tiwai@suse.de>
>> > A simple approach would be adding a control element containing
>> > byte-array of ELD/EDID.
>>
>> Are there any examples of such controls? Or are we talking about a new
>> kind of control?
>
> Look for SNDRV_CTL_ELEM_TYPE_BYTES. Some codecs provide these.
I started doing some work on this, adding a persistent 256-byte buffer
to store the ELD data instead of dynamically allocating and freeing
the buffer. I am kind of lost with the controls though, never looked
at this part of ALSA before.
In all the HDA code, all controls have an IFACE_MIXER type, while all
the code that uses ELEM_TYPE_BYTES the type is IFACE_PCM. Does this
matter at all?
Likewise, there's a 'generic_hdmi_build_controls' routine in which I
could add the ELD control, but it uses cvt structures. I think it
would make more sense to relate ELD controls to pins, as done with the
proc information.
Quite a learning experience...
next prev parent reply other threads:[~2011-05-18 15:43 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 [this message]
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='BANLkTi=oR9VoW8TbgicF0Zg3bSS46kwbkA@mail.gmail.com' \
--to=bossart.nospam@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--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).