Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org
Subject: Re: [RFC PATCH 1/2] ALSA: hda - Fix "PCM" name being used on one DAC when there are two DACs
Date: Thu, 16 Oct 2014 17:10:22 +0200	[thread overview]
Message-ID: <543FDFDE.7040800@canonical.com> (raw)
In-Reply-To: <CAN8cciZAteQAaG9GAxwLWyF6u5xH_fGtRDOTq5j+4LNoj_d_jA@mail.gmail.com>


On 2014-10-16 17:02, Raymond Yau wrote:
>
>
> >
> > In the scenario where there is one "Line Out", one "Speaker" and one
> > "Headphone", and there are only two DACs, two outputs will share a DAC.
> > Currently any mixer on such a DAC will get the "PCM" name, which is
> > misleading. Instead use "Headphone+LO" or "Speaker+LO" to better
> > specify what the volume actually controls.
>
> Are there any examples ?
>

I used "hda-emu 
codecs/canonical/alc3226-dell-precision-m2800-ccert-201404-14986 -i 1" 
when developing the patches.

I don't have any hardware available myself that exposes this behavior, 
but I can maybe fake one with hdajackretask, if that counts...

// David

  reply	other threads:[~2014-10-16 15:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-16 13:33 [RFC PATCH 1/2] ALSA: hda - Fix "PCM" name being used on one DAC when there are two DACs David Henningsson
2014-10-16 13:33 ` [RFC PATCH 2/2] ALSA: hda - Use "Line Out" name instead of "PCM" when there are other outputs David Henningsson
2014-10-16 14:54 ` [RFC PATCH 1/2] ALSA: hda - Fix "PCM" name being used on one DAC when there are two DACs Takashi Iwai
2014-10-16 15:02 ` Raymond Yau
2014-10-16 15:10   ` David Henningsson [this message]
2014-10-18 12:33     ` Raymond Yau
2014-10-18 18:28       ` Takashi Iwai
2014-10-18 23:02         ` Raymond Yau
2014-10-19  9:02           ` Takashi Iwai
2014-10-20  1:10             ` Raymond Yau
2014-10-20  5:54               ` Takashi Iwai
2014-10-20  6:29           ` David Henningsson
2014-10-20  9:55             ` Raymond Yau
2014-10-20  9:58               ` Takashi Iwai
2014-10-20 11:31                 ` Raymond Yau
2014-10-20 11:48                   ` Takashi Iwai
2014-10-20 14:24                     ` Raymond Yau
2014-10-20 14:33                       ` Takashi Iwai
2014-10-20 23:37                         ` Raymond Yau
2014-10-21  2:29                       ` Robert Hancock
2014-10-21  7:55                         ` Raymond Yau
2014-10-21 13:06                           ` Raymond Yau
2014-10-22  7:43                     ` Raymond Yau
2014-10-20  9:59               ` David Henningsson
2014-10-20 10:02                 ` Takashi Iwai
2014-10-20 10:15                   ` David Henningsson
2014-10-20 11:27                     ` Takashi Iwai
2014-10-22  7:29                   ` Takashi Iwai
2014-10-20 14:38                 ` Raymond Yau

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=543FDFDE.7040800@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=superquad.vortex2@gmail.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