From: Matthew Ranostay <mranostay@embeddedalley.com>
To: Mario Limonciello <mario_limonciello@dell.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] hda: Add logic to force HP mixer creation
Date: Tue, 17 Feb 2009 15:42:02 -0500 [thread overview]
Message-ID: <499B211A.1040509@embeddedalley.com> (raw)
In-Reply-To: <499B0F90.4070008@dell.com>
Mario Limonciello wrote:
> Hi Takashi:
>
> Takashi Iwai wrote:
>> If "Surround" doesn't do anything, why should it be there?
>> And, does "Headphone" change both headphones even with 4 or 6 ch outputs
>> properly? Doesn't "Headhpone" change any other output volumes?
>>
> I found what the surround mixer is being used for. If "Mic as Output" is
> turned on, "Surround" acts as the mixer to control that jack.
>
Correct.
The the reason the headphone mixer isn't created without my patch is the "mic as output"
and "line in as output" switches.
> The Headphone mixer changes both of the regular headphone jack's
> volumes. Changing the "Headphone" volume doesn't affect the speaker
> outputs at all, only the two headphone jacks.
>> The patch introduces another exception, and now nobody would understand
>> how the channels and outputs and mixers are assigned together.
>>
> Two points:
> 1) I'm not sure this is as much of a problem as you raise. I don't
> believe many people even know how the channels and mixers are assigned
> in the first place. I see plenty of support requests for "why doesn't
> this second headphone jack work with headphones". I've never seen one of
> "I can't hook up my 7.1 surround system to my consumer grade laptop and
> have all of my speakers work". These machines come with DisplayPort and
> HDMI ports which people will generally be using for hooking up to their
> television sets. I seem to think it's not very common to use the
> analogue jacks to independently hook up pairs of speakers assigned to
> say Front or Surround.
> 2) You are still able to hook up a separate set of speakers to the mic
> output jack and since those are assigned surround have things work as
> expected.
>
>> Hm, I thought I did. Which patch exactly?
>>
>>
> The patch title was [PATCH] hda: Add STA_DELL_S14 quirk. Here's the
> starting part of it:
>
> Add STAC_DELL_S14 quirk for new laptop series. Removed un-needed pins in pin_nids
> for stac92hd83xxx. Also reorganized connection selection code for the respective ports
> per quirk define.
>
> ---
> sound/pci/hda/patch_sigmatel.c <imap://mario_limonciello@outlook.dell.com:143/fetch%3EUID%3E/INBOX%3E13699#sound/pci/hda/patch_sigmatel.c> | 52 +++++++++++++++++++++++++++-------------
>
>
> 1 files changed, 35 insertions(+), 17 deletions(-)
>
>
> You responded to the mail saying it was applied, but I seem to not be
> able to find it in current ALSA git.
>
> Regards
next prev parent reply other threads:[~2009-02-17 20:42 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 [this message]
2009-02-17 20:44 ` Takashi Iwai
2009-02-17 21:06 ` Mario Limonciello
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=499B211A.1040509@embeddedalley.com \
--to=mranostay@embeddedalley.com \
--cc=alsa-devel@alsa-project.org \
--cc=mario_limonciello@dell.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.