From: Takashi Iwai <tiwai@suse.de>
To: "Rafael Espíndola" <rafael.espindola@gmail.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Fwd: [PATCH] sound working on the macbook pro
Date: Mon, 12 Mar 2007 16:00:38 +0100 [thread overview]
Message-ID: <s5hwt1mjyll.wl%tiwai@suse.de> (raw)
In-Reply-To: <564d96fb0703092157t5b7f171cr1f94125cac32b782@mail.gmail.com>
At Fri, 9 Mar 2007 21:57:45 -0800,
=?UTF-8?Q?Rafael_Esp=C3=ADndola?= wrote:
>
> > Then it means that stac92xx_hp_detect() isn't called properly, or the
> > pin-detection doesn't work with your hardware. Otherwise
> > stac92xx_auto_init_multiout() should enable this pin. Could you check
> > whether stac92xx_hp_detect() is called and how is it processed
> > (e.g. by adding printk's)? Also, add a printk in
> > stac92xx_auto_init_multiout() to make sure that this isn't called.
>
> all tests performed with the new pin config.
> with the fix-up enabled:
> *) stac92xx_auto_init_multi_out is not called
> *) stac92xx_hp_detect is called:
> cfg->hp_outs = 1
> presence = 0 after the first loop
> cfg->line_outs = 3
> cfg->speaker_outs = 0
> *) speakers don't work
>
> with the fix-up disabled:
> *) stac92xx_auto_init_multi_out in not called
> *) stac92xx_hp_detect is called:
> cfg->hp_outs = 1
> presense = 0 after the first loop
> cfg->line_outs = 0
> cfg->speaker_outs = 1
> *) speakers work
I guess it's a missing initialization for the first line-out jack.
It works on ohter devices because the default PIN setup has
AC_PIN_OUT_EN. But, on Mac, it has AC_PIN_IN_EN by some reason.
The patch below should fix the problm. Give it a try.
Takashi
diff -r e87b2114ceae pci/hda/patch_sigmatel.c
--- a/pci/hda/patch_sigmatel.c Mon Mar 12 12:54:23 2007 +0100
+++ b/pci/hda/patch_sigmatel.c Mon Mar 12 15:56:58 2007 +0100
@@ -1600,6 +1600,11 @@ static int stac92xx_init(struct hda_code
for (i = 0; i < cfg->hp_outs; i++)
enable_pin_detect(codec, cfg->hp_pins[i],
STAC_HP_EVENT);
+ /* force to enable the first line-out; the others are set up
+ * in unsol_event
+ */
+ stac92xx_auto_set_pinctl(codec, spec->autocfg.line_out_pins[0],
+ AC_PINCTL_OUT_EN);
stac92xx_auto_init_hp_out(codec);
/* fake event to set up pins */
codec->patch_ops.unsol_event(codec, STAC_HP_EVENT << 26);
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-12 15:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-18 17:06 [PATCH] sound working on the macbook pro Rafael Espíndola
[not found] ` <564d96fb0702180924y32118e7esf81e5ec2514d3af9@mail.gmail.com>
2007-02-19 11:52 ` Fwd: " Takashi Iwai
2007-02-20 9:40 ` Rafael Espíndola
2007-02-20 12:05 ` Takashi Iwai
2007-02-20 20:05 ` Rafael Espíndola
2007-02-22 15:46 ` Takashi Iwai
2007-02-22 20:01 ` Rafael Espíndola
2007-02-23 14:32 ` Takashi Iwai
[not found] ` <564d96fb0702262134t438dd480t45c83e556f315e2e@mail.gmail.com>
2007-03-07 23:01 ` Takashi Iwai
2007-03-10 5:57 ` Rafael Espíndola
2007-03-12 15:00 ` Takashi Iwai [this message]
2007-03-13 7:14 ` Rafael Espíndola
2007-03-13 9:41 ` 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=s5hwt1mjyll.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rafael.espindola@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