From: Mario Limonciello <mario_limonciello@dell.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
Matthew Ranostay <mranostay@embeddedalley.com>
Subject: Re: [PATCH] hda: Add logic to force HP mixer creation
Date: Tue, 17 Feb 2009 15:06:38 -0600 [thread overview]
Message-ID: <499B26DE.2010109@dell.com> (raw)
In-Reply-To: <s5hljs46beo.wl%tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 2189 bytes --]
Hi Takashi:
Takashi Iwai wrote:
> At Tue, 17 Feb 2009 13:27:12 -0600,
> Mario Limonciello wrote:
>
>
> Ah, OK, then the mic jack is connected to the surround DAC.
> But don't you have Center and LFE?
>
There aren't mixers for Center or LFE at all. Again going back to my
feelings about mixer names, for the purposes of a laptop I think
providing a knob called Center or another called LFE just adds to the
confusion.
> And any control of speaker volume?
>
Speaker volume is handled by the combination of Master, PCM, and Front
mixers. The headphone mixer has no bearing on the volume of the speakers.
>
> And exactly this is another point why I feel the necessity of
> cleanup. If the feature isn't needed, we should get rid of it. Or,
> implement in a better form.
>
If I was to put a vote towards this, I think attempting to support 6
channel analog in the mobile space is a feature that needs to go. It
causes confusion and complicates the code.
> One more another problem is that this setup thingy isn't described
> at all, or pretty hard to guess from the mixer control. There are
> knobs, but you don't know the combination.
>
I think knobs, switches, do-hickeys, etc are great to have when they
serve an explicit purpose. I look at the mixers being presented to me,
and I've no idea what
"Mono Mux" is there for, or why I've got several "Digital Input Source"
areas.
> This must be included. Check commit
> 8bb0ac5573ff0879fef511e1a80a4a4db0316daa
> in sound git tree.
>
I suppose i've got some confusion for when these commits are showing up
on
http://git.alsa-project.org/?p=alsa-kernel.git;a=history;f=sound/pci/hda/patch_sigmatel.c;h=3c84817ccd2e0d4bd1eee4f2882047ae84165e10;hb=HEAD
My understanding was that the tree alsa-kernel tree was merged into the
alsa-driver and alsa-kmirror trees on a regular basis. I have been
operating off of web snapshots of alsa-driver from
http://www.alsa-project.org/snapshot/ since I can't do GIT internally
here, but I'm not seeing the patch show up in alsa-driver there.
Regards
--
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@dell.com
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2009-02-17 21:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 16:01 [PATCH] hda: Add logic to force HP mixer creation Matthew Ranostay
2009-02-16 9:08 ` Takashi Iwai
2009-02-16 23:34 ` Matthew Ranostay
2009-02-17 17:16 ` Takashi Iwai
2009-02-17 18:02 ` Mario Limonciello
2009-02-17 18:28 ` Takashi Iwai
2009-02-17 19:27 ` Mario Limonciello
2009-02-17 20:42 ` Matthew Ranostay
2009-02-17 20:44 ` Takashi Iwai
2009-02-17 21:06 ` Mario Limonciello [this message]
2009-02-18 6:43 ` 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=499B26DE.2010109@dell.com \
--to=mario_limonciello@dell.com \
--cc=alsa-devel@alsa-project.org \
--cc=mranostay@embeddedalley.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 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.