alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: "Viliam Kubis" <viliam.kubis@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>,
	Raymond Yau <superquad.vortex2@gmail.com>
Subject: Re: Smart 5.1 function not working on VIA VT1708S with *three* jacks on mainboard
Date: Sat, 10 Jul 2010 14:39:11 +0200	[thread overview]
Message-ID: <op.vfmn3k2py9cctd@localhost> (raw)
In-Reply-To: <AANLkTim0B4gB4X1SfURg_NF4-gnJ3GTGjCH1PIVwBtfD@mail.gmail.com>

But my speakers only come with two jacks for input. One for the front  
speakers and one for rear speakers. So I cannot connect the speakers to  
all three jacks. I have compiled alsa with --with-debug=full configure  
option to see which pins it has auto-parsed:

HDA Intel 0000:00:14.2: PCI INT A disabled
HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ALSA hda_codec.c:4408: autoconfig: line_outs=1 (0x1c/0x0/0x0/0x0/0x0)
ALSA hda_codec.c:4412:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
ALSA hda_codec.c:4416:    hp_outs=1 (0x1d/0x0/0x0/0x0/0x0)
ALSA hda_codec.c:4417:    mono: mono_out=0x0
ALSA hda_codec.c:4420:    dig-out=0x20/0x0
ALSA hda_codec.c:4428:    inputs: mic=0x1a, fmic=0x1e, line=0x1b,  
fline=0x0, cd=0x1f, aux=0x0

However in function smart51_get, the following condition

if (ctl & AC_PINCTL_IN_EN
     && !(ctl & AC_PINCTL_OUT_EN))
{
	printk(KERN_INFO "*** PATCH on=0 in via_smart51_get()");
	on = 0;
}

will never be true, so smart51_get will always set  
*ucontrol->value.integer.value to 1. (printk line will not execute)

Smart 5.1 control gets created and appears to be "working". However  
surround output does not work.

On Sat, 10 Jul 2010 11:41:35 +0200, Raymond Yau  
<superquad.vortex2@gmail.com> wrote:

>>> It might be. It is important not to mix VT1708 and VT1708S. For  
>>> VT1708S,
> the following DACs are used in code:
>
>   /* config dac list */
>   switch (i) {
>   case AUTO_SEQ_FRONT:
>   	spec->multiout.dac_nids[i] = 0x10;
>   	break;
>   case AUTO_SEQ_CENLFE:
>   	spec->multiout.dac_nids[i] = 0x24;
>   	break;
>   case AUTO_SEQ_SURROUND:
>   	spec->multiout.dac_nids[i] = 0x11;
>   	break;
>   case AUTO_SEQ_SIDE:
>   	spec->multiout.dac_nids[i] = 0x25;
>   	break;
>   }
>
>>>  So 0x12 is not used for any of the surround outputs.
>
> I think your testing config is not compiled with smart 5.1 requirement
>
> Refer to smart51_get() , this function exepct red jack and blue jack
> are configued to Output
>
> But you still plugged in Mic into the pink jack according to your photo.
>
> Your speakers have to plugged in both pink and blue jacks
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel


-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

  reply	other threads:[~2010-07-10 12:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-10  9:41 Smart 5.1 function not working on VIA VT1708S with *three* jacks on mainboard Raymond Yau
2010-07-10 12:39 ` Viliam Kubis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-06-30 22:02 Viliam Kubis
2010-07-06 22:19 ` Fwd: " Viliam Kubis
2010-07-08  6:33   ` Clemens Ladisch
2010-07-09  1:32     ` Raymond Yau
     [not found]       ` <op.vfkm5fn9y9cctd@localhost>
2010-07-09 11:05         ` Viliam Kubis
     [not found]     ` <op.vfi12awty9cctd@localhost>
2010-07-09 11:04       ` Viliam Kubis
     [not found]     ` <op.vfi2hgary9cctd@localhost>
2010-07-09 11:05       ` Viliam Kubis
2010-07-12  6:57         ` Clemens Ladisch
2010-07-12 10:58           ` Viliam Kubis
2010-07-22 20:36             ` Simon Schubert

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=op.vfmn3k2py9cctd@localhost \
    --to=viliam.kubis@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=superquad.vortex2@gmail.com \
    /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).