From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: First test of the hda-jack branch
Date: Mon, 21 Nov 2011 11:02:11 +0100 [thread overview]
Message-ID: <4ECA21A3.9080700@canonical.com> (raw)
In-Reply-To: <s5hk46yln3i.wl%tiwai@suse.de>
On 11/17/2011 05:39 PM, Takashi Iwai wrote:
> At Mon, 14 Nov 2011 10:32:07 +0100,
> Takashi Iwai wrote:
>>
>>> In addition, I have a question about the second machine, which looks
>>> like this:
>>>
>>> numid=45,iface=CARD,name='Front Headphone Jack'
>>> numid=47,iface=CARD,name='Front Mic Jack'
>>> numid=48,iface=CARD,name='Line Jack'
>>> numid=41,iface=CARD,name='Line-Out Jack'
>>> numid=42,iface=CARD,name='Line-Out Jack',index=1
>>> numid=43,iface=CARD,name='Line-Out Jack',index=2
>>> numid=44,iface=CARD,name='Line-Out Jack',index=3
>>> numid=46,iface=CARD,name='Rear Mic Jack'
>>>
>>> Would it be possible to name the Line-Out Jacks "Front Line-Out",
>>> "Surround Line-Out" etc, so one can tell which one is which? Or can you
>>> always tell that just from the order of them?
>>
>> I can assign more intuitive names for the output, certainly.
>> I'll consider the implementation.
>
> I added more commits there for a bit better control names.
> The function got messy and I'd need to rewrite sometime later, but
> would like to complete the feature at first.
>
> Note that along with the development, I had to rebase this branch so
> that it can be merged easily to the latest tree. Please be careful
> when you pull to the existing branch.
Thanks! I've only had a quick look so far (no real test yet), I have
some thoughts though:
1) I like the idea of having location prefix and channel mapping suffix!
With this implementation we also seem to avoid things like "Front
Line-Out Rear" and "Rear Line-Out Front" which could have been
confusing, so well done :-)
2) I saw that headphones were not handled differently, for dual
headphones, could they be called e g "Headphone Front Jack" and
"Headphone Surround Jack" even they both play the front channel?
3) For HDMI I added a while ago something to make it possible to
associate the HDMI Jack name with the correct PCM device. We must do the
same for the kctl implementation, or it will not be possible to
distinguish them correctly. I suggest we do like with the ELD control
here, and set the "device" of the kcontrol to 3,7,8 or 9. Do you agree?
(We can also add this number somewhere in the name, which might be
simpler but maybe less elegant.)
4) "Surround" is misspelled in check_output_sfx.
Thanks,
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2011-11-21 10:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 16:23 First test of the hda-jack branch David Henningsson
2011-11-11 16:52 ` Takashi Iwai
2011-11-11 20:08 ` David Henningsson
2011-11-14 9:32 ` Takashi Iwai
2011-11-14 16:24 ` Jaroslav Kysela
2011-11-15 9:22 ` David Henningsson
2011-11-16 9:50 ` Raymond Yau
2011-11-16 10:07 ` David Henningsson
2011-11-17 16:39 ` Takashi Iwai
2011-11-21 10:02 ` David Henningsson [this message]
2011-11-21 13:38 ` Takashi Iwai
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=4ECA21A3.9080700@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--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 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.