From: Raymond Yau <superquad.vortex2@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Via VT2020: issues with kernel 2.6.38.{2, 3} (alsa 1.0.23) - working with 2.6.33.2 (alsa 1.0.21)
Date: Tue, 14 Jun 2011 12:05:06 +0800 [thread overview]
Message-ID: <BANLkTim7-J8ofdtqcdmKYnzfLocMajdo7w@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimJb-UMD5Nk3d+_GW-b9Cir13PjMw@mail.gmail.com>
2011/6/8 alex dot baldacchino dot alsasub at gmail dot com
<alex.baldacchino.alsasub@gmail.com>:
>
>
> http://pastebin.ca/2076750
>
>
> By the way, should something like the above be done for capture
> streams as well? I've noticed (with front panel disabled) that
> controls "Front Mic Playback Volume" and "Front Mic Playback Switch"
> are correctly missing from audio-mixer widget 0x21, but node 0x29 is
> still 'attached' to control "Front Mic Boost Capture Volume", which is
> accessible through a mixer (though I didn't try to play with it; it is
> listed also by amixer output in above linked document). Is this the
> wanted/expected behaviour?
It seem that 0x2b and 0x29 does not have any mic boost capture volume,
that look like "Playback Switch" when they are retasked as output for
3 jacks motherboard
Node 0x29 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
Control: name="Front Mic Boost Capture Volume", index=0, device=0
ControlAmp: chs=3, dir=In, idx=0, ofs=0
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x80 0x80]
Pincap 0x0000233c: IN OUT HP Detect
Vref caps: HIZ 50 100
Pin Default 0x02a19037: [Jack] Mic at Ext Front
Conn = 1/8, Color = Pink
DefAssociation = 0x3, Sequence = 0x7
Pin-ctls: 0x21: IN VREF_50
Unsolicited: tag=20, enabled=1
Power states: D0 D1 D2 D3
Power: setting=D3, actual=D3
Connection: 1
0x1c
Node 0x2b [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
Control: name="Mic Boost Capture Volume", index=0, device=0
ControlAmp: chs=3, dir=In, idx=0, ofs=0
Amp-Out caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1
Amp-Out vals: [0x80 0x80]
Pincap 0x00002334: IN OUT Detect
Vref caps: HIZ 50 100
Pin Default 0x01a19036: [Jack] Mic at Ext Rear
Conn = 1/8, Color = Pink
DefAssociation = 0x3, Sequence = 0x6
Pin-ctls: 0x21: IN VREF_50
Unsolicited: tag=20, enabled=1
Power states: D0 D1 D2 D3
Power: setting=D0, actual=D0
Connection: 2
0x0a* 0x0c
/* capture mixer elements */
static const struct snd_kcontrol_new vt1718S_capture_mixer[] = {
HDA_CODEC_VOLUME("Capture Volume", 0x10, 0x0, HDA_INPUT),
HDA_CODEC_MUTE("Capture Switch", 0x10, 0x0, HDA_INPUT),
HDA_CODEC_VOLUME_IDX("Capture Volume", 1, 0x11, 0x0, HDA_INPUT),
HDA_CODEC_MUTE_IDX("Capture Switch", 1, 0x11, 0x0, HDA_INPUT),
- HDA_CODEC_VOLUME("Mic Boost Capture Volume", 0x2b, 0x0, HDA_INPUT),
- HDA_CODEC_VOLUME("Front Mic Boost Capture Volume", 0x29, 0x0,
- HDA_INPUT),
(I understand there must be, anyway, two
> captures and two input sources, because there's still one line-in plus
> one (rear) mic, plus stereo-mix to deal with, and one "boost capture
> volume" control for the rear mic does make sense, my doubt is about
> its corresponding control for the now missing front mic).
>
The problem is in hda_verb vt1718S_volume_init_verbs
/* Amp Indices: CD = 1, Mic1 = 2, Line = 3, Mic2 = 4 */
{0x21, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_MUTE(0)},
{0x21, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_MUTE(1)},
{0x21, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_MUTE(2)},
{0x21, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_MUTE(3)},
{0x21, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_UNMUTE(5)},
node 0x21 of your vt2020 has only 5 connections
Refer to commit 4ab2d53a99b6dcee86837d2a9739bfb9f468db45
you will need to ask the author of this patch since the patch
explicitly change this non exisiting connection of node 0x21 on your
vt2020
- {0x21, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_MUTE(5)},
+ {0x21, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_UNMUTE(5)},
Node 0x21 [Audio Mixer] wcaps 0x20050b: Stereo Amp-In
Control: name="Front Mic Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=In, idx=3, ofs=0
Control: name="Front Mic Playback Switch", index=0, device=0
ControlAmp: chs=3, dir=In, idx=3, ofs=0
Control: name="Rear Mic Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=In, idx=1, ofs=0
Control: name="Rear Mic Playback Switch", index=0, device=0
ControlAmp: chs=3, dir=In, idx=1, ofs=0
Control: name="Line Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=In, idx=2, ofs=0
Control: name="Line Playback Switch", index=0, device=0
ControlAmp: chs=3, dir=In, idx=2, ofs=0
Amp-In caps: ofs=0x17, nsteps=0x1f, stepsize=0x05, mute=1
Amp-In vals: [0x80 0x80] [0x1f 0x1f] [0x1f 0x1f] [0x1f 0x1f] [0x97 0x97]
Power states: D0 D1 D2 D3
Power: setting=D0, actual=D0
Connection: 5
0x2c 0x2b 0x2a 0x29 0x28
next prev parent reply other threads:[~2011-06-14 4:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-07 17:30 Via VT2020: issues with kernel 2.6.38.{2, 3} (alsa 1.0.23) - working with 2.6.33.2 (alsa 1.0.21) alex dot baldacchino dot alsasub at gmail dot com
2011-05-08 6:40 ` Raymond Yau
2011-05-08 23:16 ` alex dot baldacchino dot alsasub at gmail dot com
2011-05-10 2:03 ` Raymond Yau
2011-05-16 16:03 ` alex dot baldacchino dot alsasub at gmail dot com
2011-05-18 3:36 ` Raymond Yau
2011-05-27 14:49 ` alex dot baldacchino dot alsasub at gmail dot com
2011-05-31 13:34 ` Raymond Yau
2011-06-01 16:16 ` alex dot baldacchino dot alsasub at gmail dot com
2011-06-07 8:32 ` Raymond Yau
2011-06-08 14:33 ` alex dot baldacchino dot alsasub at gmail dot com
2011-06-09 16:08 ` alex dot baldacchino dot alsasub at gmail dot com
2011-06-11 20:24 ` alex dot baldacchino dot alsasub at gmail dot com
2011-06-19 1:46 ` Raymond Yau
2011-06-20 1:19 ` alex dot baldacchino dot alsasub at gmail dot com
2011-06-20 7:13 ` Raymond Yau
2011-06-20 13:48 ` alex dot baldacchino dot alsasub at gmail dot com
2011-06-14 4:05 ` Raymond Yau [this message]
2011-06-18 8:29 ` Raymond Yau
2011-06-19 12:44 ` alex dot baldacchino dot alsasub at gmail dot com
-- strict thread matches above, loose matches on Subject: below --
2011-06-16 18:50 alex dot baldacchino dot alsasub at gmail dot com
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=BANLkTim7-J8ofdtqcdmKYnzfLocMajdo7w@mail.gmail.com \
--to=superquad.vortex2@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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;
as well as URLs for NNTP newsgroup(s).