From: David Henningsson <david.henningsson@canonical.com>
To: Raymond Yau <superquad.vortex2@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, ruedi@battle-eggs.de
Subject: Re: [RFC PATCH 1/2] ALSA: hda - Fix "PCM" name being used on one DAC when there are two DACs
Date: Mon, 20 Oct 2014 11:59:30 +0200 [thread overview]
Message-ID: <5444DD02.1070608@canonical.com> (raw)
In-Reply-To: <CAN8cciYCSd8QqHNZ=7ip_-YnG1ru9jJ3rjW8S_YjyrhRLGBFzA@mail.gmail.com>
On 2014-10-20 11:55, 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...
> >> > > >
> >> > >
> >> > > How about adding these names to slaves of virtual master
> >> volume/switch ?
> >> > >
> >> > > hdajackretask won't help if the topology of the codecs are
> different
> >> > >
> >> > > Seem the badness still prevent the driver to support surround
> 5.1 with
> >> > > three rear panel jacks, internal speaker and front panel
> headphone for
> >> > > Thinkcenter A58 using alc662
> >> > >
> >> > >
> >>
> https://www.mail-archive.com/alsa-user@lists.sourceforge.net/msg29203.html
> >> > >
> >> > > Why 3stack desktops with 6 channels codecs not using
> >> "Headphone+LO" or
> >> > > "Speaker+LO" ?
> >> >
> >> > The problem is just the lack of DACs, so it cannot cover all three
> >> > outputs, no matter how the pins are chosen. That is, it's no 6
> >> > channels at all but 4 channels at most.
> >> >
> >> >
> >>
> >> http://shop.lenovo.com/us/en/desktops/thinkcentre/a-series/a58/
> >>
> >> The technical specification of a58
> >>
> >> 2 pin internal speaker connector
> >> Alc662 5.1
> >>
> >> https://bbs.archlinux.org/viewtopic.php?id=156433
> >>
> >> Seem windows support surround 5.1
> >
> >
> > Raymond, there can certainly be cases which this patch does not cover
> - after all, it's mostly a band aid given the lack of topology
> information - but do you see cases where this patch actually causes a
> *regression*? If so, could you point me to alsa-info for the machine
> where this patch causes a regression?
> >
>
> www.realtek.com.tw/products/productsView.aspx?Langid=1&PNid=24&PFid=27&Level=5&Conn=4
> <http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PNid=24&PFid=27&Level=5&Conn=4>
>
> I expect those desktop with 2+2 HD Audio codec support independent headphone
>
> This mean the driver should not create "Lineout+HP" Playback volume
>
> Line out and headphone cannot share same DAC
I doubt that, but if they cannot share the same DAC, that needs to be
addressed in a separate patch. This patch just deals with the naming,
given that the previous logic has determined that headphone and Line out
should share the same DAC.
Takashi, are you planning to apply this patch? Or are you looking for
more testing first?
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next prev parent reply other threads:[~2014-10-20 9:59 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
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 [this message]
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=5444DD02.1070608@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=ruedi@battle-eggs.de \
--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 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.