alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: 107 <107@mail.ru>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] Sony Vaio with stac9872
Date: Mon, 27 Feb 2012 11:04:19 +0100	[thread overview]
Message-ID: <s5hty2cwq1o.wl%tiwai@suse.de> (raw)
In-Reply-To: <E1S0uT1-0000JE-FI.107-mail-ru@f35.mail.ru>

At Fri, 24 Feb 2012 16:41:43 +0400,
107 wrote:
> 
> Hello, I have no sound on my Sony Vaio SZ4XRN laptop with newest kernels.
> Sound: hda-intel, sigmatel - STAC9872
> 
> To solve this issue I make this patch for sound/pci/hda/patch_sigmatel.c:
> 
> --- patch_sigmatel.c.bak        2012-02-23 21:01:28.577515317 +0400
> +++ patch_sigmatel.c    2012-02-23 21:53:21.035605216 +0400
> @@ -6357,7 +6357,16 @@
>   */
>  
>  static const struct hda_verb stac9872_core_init[] = {
> -       {0x15, AC_VERB_SET_CONNECT_SEL, 0x1}, /* mic-sel: 0a,0d,14,02 */
> +       {0x0a, AC_VERB_SET_PIN_WIDGET_CONTROL, PIN_HP }, /* HP <- 0x2 */
> +       {0x0f, AC_VERB_SET_PIN_WIDGET_CONTROL, PIN_OUT }, /* Speaker <- 0x5 */
> +       {0x0d, AC_VERB_SET_PIN_WIDGET_CONTROL, PIN_VREF80 }, /* Mic? (<- 0x2) */
> +       {0x0e, AC_VERB_SET_PIN_WIDGET_CONTROL, PIN_IN }, /* CD */
> +       {0x14, AC_VERB_SET_PIN_WIDGET_CONTROL, PIN_VREF80 }, /* Mic? */
> +       {0x15, AC_VERB_SET_CONNECT_SEL, 0x2 /*0x1*/ }, /* mic-sel: 0a,0d,14,02 */
> +       {0x02, AC_VERB_SET_AMP_GAIN_MUTE, AMP_OUT_MUTE}, /* HP */
> +       {0x05, AC_VERB_SET_AMP_GAIN_MUTE, AMP_OUT_MUTE}, /* Speaker */
> +       {0x09, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_MUTE(0)}, /* capture sw/vol -> 0x8 */
> +       {0x07, AC_VERB_SET_AMP_GAIN_MUTE, AMP_IN_UNMUTE(0)}, /* CD-in -> 0x6 */
>         {0x15, AC_VERB_SET_AMP_GAIN_MUTE, AMP_OUT_UNMUTE}, /* Mic-in -> 0x9 */
>         {}
>  };
> 
> 
> Constants got from old kernel (2.6.22).
> With this patch sound works fine. Thank you. 

Most of verbs above must be superfluous, but some of them might be
needed in your case.  Could you give alsa-info.sh outputs (run with
--no-upload option) on both working and non-working cases?


thanks,

Takashi

  reply	other threads:[~2012-02-27 10:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 12:41 [PATCH] Sony Vaio with stac9872 107
2012-02-27 10:04 ` Takashi Iwai [this message]
     [not found]   ` <CAJ=7qUP_XZneucEmPqBzWuNmSvJ8L4p8UU5=3k-mZSymb3e=Vw@mail.gmail.com>
2012-02-28  7:29     ` 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=s5hty2cwq1o.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=107@mail.ru \
    --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).