trying to get sound working at a mac book pro (core 2 duo)

trying to get sound working at a mac book pro (core 2 duo)

[Rafael Espíndola]

I have installed the alsa drivers from the mercurial repository and
the current status is

*) Headphone works
*) Speakers work
*) Headphone sensing works
*) Internal microphone doesn't

I haven't tried to use an external microphone.

Following the steps in http://www.jasonparekh.com/?page_id=9 resulted
in the microphone working but the speakers stoped.

The subsystem ID of my card is 0x106b1e00. This is the only difference
from the one on http://www.jasonparekh.com/?page_id=9.

I tried to grep for this subsystem in the windows driver (from
bootcamp 1.1.2) but it is not listed. Has someone installed windows on
one of these systems? Does sound works?

Any ideas on how to try to find out the correct pin setting? Maybe
looking at the macos driver?

And in the case I can make it work, what is the correct way to do an
switch on the subsystem? Is there a variant of
snd_hda_check_board_config that also uses subsystem ID to
disambiguate pin configs?

Thanks,
Rafael

-------------------------------------------------------------------------
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

Re: trying to get sound working at a mac book pro (core 2 duo)

[Tobin Davis]

[-- Attachment #1.1: Type: text/plain, Size: 2099 bytes --]

If you could send me the output from "lspci -s 0:1b -vn" I can add this
to the driver so you and other Mac users will work out of the box.

Using the subsystem id from the codec output isn't always accurate, and
the driver uses the output from lspci anyways.

As to internal mic, I can look into it.  Send me the output from
"cat /proc/asound/card0/codec#*" as an attachment.

Tobin

On Wed, 2007-02-14 at 19:21 +0000, Rafael Espíndola wrote:

> I have installed the alsa drivers from the mercurial repository and
> the current status is
> 
> *) Headphone works
> *) Speakers work
> *) Headphone sensing works
> *) Internal microphone doesn't
> 
> I haven't tried to use an external microphone.
> 
> Following the steps in http://www.jasonparekh.com/?page_id=9 resulted
> in the microphone working but the speakers stoped.
> 
> The subsystem ID of my card is 0x106b1e00. This is the only difference
> from the one on http://www.jasonparekh.com/?page_id=9.
> 
> I tried to grep for this subsystem in the windows driver (from
> bootcamp 1.1.2) but it is not listed. Has someone installed windows on
> one of these systems? Does sound works?
> 
> Any ideas on how to try to find out the correct pin setting? Maybe
> looking at the macos driver?
> 
> And in the case I can make it work, what is the correct way to do an
> switch on the subsystem? Is there a variant of
> snd_hda_check_board_config that also uses subsystem ID to
> disambiguate pin configs?
> 
> Thanks,
> Rafael
> 
> -------------------------------------------------------------------------
> 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
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel

-- 
Tobin Davis <tdavis@dsl-only.net>

[-- Attachment #1.2: Type: text/html, Size: 3663 bytes --]

[-- Attachment #2: Type: text/plain, Size: 345 bytes --]

-------------------------------------------------------------------------
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

[-- Attachment #3: Type: text/plain, Size: 161 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Fwd: trying to get sound working at a mac book pro (core 2 duo)

[Rafael Espíndola]

[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]

---------- Forwarded message ----------
From: Rafael Espíndola <rafael.espindola@gmail.com>
Date: Feb 14, 2007 8:09 PM
Subject: Re: [Alsa-devel] trying to get sound working at a mac book
pro (core 2 duo)
To: Tobin Davis <tdavis@dsl-only.net>


On 2/14/07, Tobin Davis <tdavis@dsl-only.net> wrote:
>
>  If you could send me the output from "lspci -s 0:1b -vn" I can add this to the driver so you and other Mac users will work out of the box.

/sbin/lspci  -s 0:1b -vn
00:1b.0 0403: 8086:27d8 (rev 02)
        Subsystem: 8384:7680
        Flags: bus master, fast devsel, latency 0, IRQ 22
        Memory at 98400000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [50] Power Management version 2
        Capabilities: [60] Message Signalled Interrupts: 64bit+
Queue=0/0 Enable-
        Capabilities: [70] Express Unknown type IRQ 0
        Capabilities: [100] Virtual Channel
        Capabilities: [130] Unknown (5)


>  Using the subsystem id from the codec output isn't always accurate, and the driver uses the output from lspci anyways.

I think that we are talking of two different subsystems :-)
There is the PCI subsystem and the HDA subsystem. The one that is
different on my mac book is the HDA subsystem.

>  As to internal mic, I can look into it.  Send me the output from "cat /proc/asound/card0/codec#*" as an attachment.

Attached

>  Tobin

Thanks,
Rafael

[-- Attachment #2: codec#0.gz --]
[-- Type: application/x-gzip, Size: 1016 bytes --]

[-- Attachment #3: Type: text/plain, Size: 345 bytes --]

-------------------------------------------------------------------------
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

[-- Attachment #4: Type: text/plain, Size: 161 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: trying to get sound working at a mac book pro (core 2 duo)

[Rafael Espíndola]

/proc/asound/card0/codec#*" as an attachment.

Note: This was generated with an unmodified hg version

Rafael

-------------------------------------------------------------------------
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

Re: trying to get sound working at a mac book pro (core 2 duo)

[Rafael Espíndola]

> I think that we are talking of two different subsystems :-)
> There is the PCI subsystem and the HDA subsystem. The one that is
> different on my mac book is the HDA subsystem.

I was reading the ICH7 document from Intel and now I am confused. The
subsystem that the document refers to is the PCI one. What subsystem
is listed in the codec file?

Rafael

-------------------------------------------------------------------------
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

Re: trying to get sound working at a mac book pro (core 2 duo)

[Rafael Espíndola]

> I was reading the ICH7 document from Intel and now I am confused. The
> subsystem that the document refers to is the PCI one. What subsystem
> is listed in the codec file?

I was really confused. The Codec also has a subsystem ID, which is
available with the verb f20 and is displayed on /proc. This is the
subsystem that is different from the two mac book versions.

Rafael

-------------------------------------------------------------------------
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

Re: trying to get sound working at a mac book pro (core 2 duo)

[Takashi Iwai]

At Wed, 14 Feb 2007 20:56:18 +0000,
=?UTF-8?Q?Rafael_Esp=C3=ADndola?= wrote:
> 
> > I was reading the ICH7 document from Intel and now I am confused. The
> > subsystem that the document refers to is the PCI one. What subsystem
> > is listed in the codec file?
> 
> I was really confused. The Codec also has a subsystem ID, which is
> available with the verb f20 and is displayed on /proc. This is the
> subsystem that is different from the two mac book versions.

The driver always takes PCI SSID as a key for table-lookup.
The codec has its own SSID (and often a different value from PCI SSID)
as proc shows, but it's not used anywhere in the driver code.


Takashi

-------------------------------------------------------------------------
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

Re: trying to get sound working at a mac book pro (core 2 duo)

[Rafael Espíndola]

> The driver always takes PCI SSID as a key for table-lookup.
> The codec has its own SSID (and often a different value from PCI SSID)
> as proc shows, but it's not used anywhere in the driver code.
Yes, but it looks like we will have to use it to disambiguate the mac books :-(

>
> Takashi
>
Rafael

-------------------------------------------------------------------------
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

Re: trying to get sound working at a mac book pro (core 2 duo)

[Tobin Davis]

[-- Attachment #1.1: Type: text/plain, Size: 728 bytes --]

On Wed, 2007-02-14 at 23:27 +0100, Takashi Iwai wrote:

> The driver always takes PCI SSID as a key for table-lookup.
> The codec has its own SSID (and often a different value from PCI SSID)
> as proc shows, but it's not used anywhere in the driver code.
> 
> 

This is the second time I've run into a system that has an HD audio
chip, but doesn't have a unique PCI SSID. The first was the Mac Pro,
where there is no SSID for the HD audio bus (see my patch for ALC885 Mac
Pro - 12/15).

Takashi, we may want to look into a function that uses the codec
subsystem id as a fallback, with the PCI SSID taking precedence.  We
already detect the HD Audio bus, through the PCI ID.  Let me know.


-- 
Tobin Davis <tdavis@dsl-only.net>

[-- Attachment #1.2: Type: text/html, Size: 1305 bytes --]

[-- Attachment #2: Type: text/plain, Size: 345 bytes --]

-------------------------------------------------------------------------
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

[-- Attachment #3: Type: text/plain, Size: 161 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Re: trying to get sound working at a mac book pro (core 2 duo)

[Takashi Iwai]

At Wed, 14 Feb 2007 17:13:20 -0800,
Tobin Davis wrote:
> 
> On Wed, 2007-02-14 at 23:27 +0100, Takashi Iwai wrote:
> 
>     The driver always takes PCI SSID as a key for table-lookup.
>     The codec has its own SSID (and often a different value from PCI SSID)
>     as proc shows, but it's not used anywhere in the driver code.
> 
> This is the second time I've run into a system that has an HD audio chip, but doesn't
> have a unique PCI SSID. The first was the Mac Pro, where there is no SSID for the HD
> audio bus (see my patch for ALC885 Mac Pro - 12/15).
> 
> Takashi, we may want to look into a function that uses the codec subsystem id as a
> fallback, with the PCI SSID taking precedence.  We already detect the HD Audio bus,
> through the PCI ID.  Let me know.

As I mentioned in another mail, so far, it'd be much easier to check
the codec SSID in each patch code rather than changing the common PCI
quirk lookup.

An experimental patch is below.  Rafael, please give it a try.


Takashi

diff -r d5fda8fa934c Documentation/ALSA-Configuration.txt
--- a/Documentation/ALSA-Configuration.txt	Wed Feb 14 15:23:57 2007 +0100
+++ b/Documentation/ALSA-Configuration.txt	Thu Feb 15 13:09:55 2007 +0100
@@ -895,10 +895,16 @@ Prior to version 0.9.0rc4 options had a 
 			can be adjusted.  Appearing only when compiled with
 			$CONFIG_SND_DEBUG=y
 
-	STAC9200/9205/9220/9221/9254
+	STAC9200/9205/9254
+	  ref		Reference board
+
+	STAC9220/9221
 	  ref		Reference board
 	  3stack	D945 3stack
 	  5stack	D945 5stack + SPDIF
+	  macmini	Intel Mac Mini
+	  macbook	Intel Mac Book
+	  macbook-pro	Intel Mac Book Pro
 
 	STAC9202/9250/9251
 	  ref		Reference board, base config
diff -r d5fda8fa934c pci/hda/patch_sigmatel.c
--- a/pci/hda/patch_sigmatel.c	Wed Feb 14 15:23:57 2007 +0100
+++ b/pci/hda/patch_sigmatel.c	Thu Feb 15 13:05:43 2007 +0100
@@ -59,6 +59,8 @@ enum {
 	STAC_D945GTP3,
 	STAC_D945GTP5,
 	STAC_MACMINI,
+	STAC_MACBOOK,
+	STAC_MACBOOK_PRO,
 	STAC_922X_MODELS
 };
 
@@ -521,11 +523,25 @@ static unsigned int d945gtp5_pin_configs
 	0x02a19320, 0x40000100,
 };
 
+static unsigned int macbook_pin_configs[10] = {
+	0x0321e230, 0x03a1e020, 0x400000fd, 0x9017e110,
+	0x400000fe, 0x0381e021, 0x1345e240, 0x13c5e22e,
+	0x400000fc, 0x400000fb,
+};
+
+static unsigned int macbook_pro_pin_configs[10] = {
+	0x0221401f, 0x90a70120, 0x01813024, 0x01014010,
+	0x400000fd, 0x01016011, 0x1345e240, 0x13c5e22e,
+	0x400000fc, 0x400000fb,
+};
+
 static unsigned int *stac922x_brd_tbl[STAC_922X_MODELS] = {
 	[STAC_D945_REF] = ref922x_pin_configs,
 	[STAC_D945GTP3] = d945gtp3_pin_configs,
 	[STAC_D945GTP5] = d945gtp5_pin_configs,
 	[STAC_MACMINI] = d945gtp5_pin_configs,
+	[STAC_MACBOOK] = macbook_pin_configs,
+	[STAC_MACBOOK_PRO] = macbook_pro_pin_configs,
 };
 
 static const char *stac922x_models[STAC_922X_MODELS] = {
@@ -533,6 +549,8 @@ static const char *stac922x_models[STAC_
 	[STAC_D945GTP5]	= "5stack",
 	[STAC_D945GTP3]	= "3stack",
 	[STAC_MACMINI]	= "macmini",
+	[STAC_MACBOOK]	= "macbook",
+	[STAC_MACBOOK_PRO]	= "macbook-pro",
 };
 
 static struct snd_pci_quirk stac922x_cfg_tbl[] = {
@@ -1866,6 +1884,23 @@ static int patch_stac922x(struct hda_cod
 	spec->board_config = snd_hda_check_board_config(codec, STAC_922X_MODELS,
 							stac922x_models,
 							stac922x_cfg_tbl);
+	if (spec->board_config == STAC_MACMINI) {
+		spec->gpio_mute = 1;
+		/* Intel Macs have all same PCI SSID, so we need to check
+		 * codec SSID to distinguish the exact models
+		 */
+		switch (codec->subsystem_id) {
+#if 0
+		case XXXX:
+			spec->board_config = STAC_MACBOOK;
+			break;
+#endif
+		case 0x106b1e00:
+			spec->board_config = STAC_MACBOOK_PRO;
+			break;
+		}
+	}
+
  again:
 	if (spec->board_config < 0) {
 		snd_printdd(KERN_INFO "hda_codec: Unknown model for STAC922x, "
@@ -1905,9 +1940,6 @@ static int patch_stac922x(struct hda_cod
 		stac92xx_free(codec);
 		return err;
 	}
-
-	if (spec->board_config == STAC_MACMINI)
-		spec->gpio_mute = 1;
 
 	codec->patch_ops = stac92xx_patch_ops;
 

-------------------------------------------------------------------------
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

Re: trying to get sound working at a mac book pro (core 2 duo)

[Rafael Espíndola]

> As I mentioned in another mail, so far, it'd be much easier to check
> the codec SSID in each patch code rather than changing the common PCI
> quirk lookup.
>
> An experimental patch is below.  Rafael, please give it a try.

It works. I have to do more tweaking on the macbook_pro_pin_configs,
but this patch is a nice improvement.

>
> Takashi

Thanks,
Rafael

-------------------------------------------------------------------------
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

Re: trying to get sound working at a mac book pro (core 2 duo)

[tdavis]

Quoting Rafael Espíndola <rafael.espindola@gmail.com>:

>> As I mentioned in another mail, so far, it'd be much easier to check
>> the codec SSID in each patch code rather than changing the common PCI
>> quirk lookup.
>>
>> An experimental patch is below.  Rafael, please give it a try.
>
> It works. I have to do more tweaking on the macbook_pro_pin_configs,
> but this patch is a nice improvement.
>
>>
>> Takashi
>
> Thanks,
> Rafael



You can get documentation on your codec here:   
http://www.idt.com/?app=search&searchType=document&categoryID=9452416

Tobin


-------------------------------------------------------------------------
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

Re: trying to get sound working at a mac book pro (core 2 duo)

[Takashi Iwai]

At Thu, 15 Feb 2007 19:55:06 +0000,
=?UTF-8?Q?Rafael_Esp=C3=ADndola?= wrote:
> 
> > As I mentioned in another mail, so far, it'd be much easier to check
> > the codec SSID in each patch code rather than changing the common PCI
> > quirk lookup.
> >
> > An experimental patch is below.  Rafael, please give it a try.
> 
> It works. I have to do more tweaking on the macbook_pro_pin_configs,
> but this patch is a nice improvement.

OK, now I committed the (slightly modified) patch to HG tree.
If you find more better pin configs, please create a patch on the top
of HG tree and submit it here (and me to Cc).

BTW, does anyone know which codec SSID does MacBook (no Pro) have?
We can add a similiar check like MacBook Pro.


Thanks,

Takashi

-------------------------------------------------------------------------
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

Re: trying to get sound working at a mac book pro (core 2 duo)

[Rafael Espíndola]

> OK, now I committed the (slightly modified) patch to HG tree.
> If you find more better pin configs, please create a patch on the top
> of HG tree and submit it here (and me to Cc).

Looking at the ioreg output on mac os I was able to find 4 different configs:

static unsigned int macbook_pro_pin_configs_2[10] = {
        0x012b4050, 0x90a00110, 0x90100140, 0x400000f0,
        0x400000f0, 0x018b3020, 0x014be060, 0x01cbe030,
        0x400000f0, 0x400000f0,
};

static unsigned int macbook_pro_pin_configs_4[10] = {
        0x012b4050, 0x90a00110, 0x90100140, 0x90100141,
        0x400000f0, 0x018b3020, 0x014be060, 0x01cbe030,
        0x400000f0, 0x400000f0
};

static unsigned int macbook_pro_pin_configs_6[10] = {
        0x012b4040, 0x90a00110, 0x90100130, 0x400000f0,
        0x400000f0, 0x018b3020, 0x014be050, 0x400000f0,
        0x400000f0, 0x400000f0
};

static unsigned int macbook_pro_pin_configs_8[10] = {
        0x012b4040, 0x400000f0, 0x90100130, 0x400000f0,
        0x400000f0, 0x018b3010, 0x014be050, 0x01cbe020,
        0x400000f0, 0x400000f0
};

the config number 2 almost works. I had to replace 0x018b3020, with
0x010b3020. I.e. replace the line-in with an dummy line-out. With this
modification I have the following items on alsamixer:

headphone, PCM, Front, Mic as Output, IEC958, Capture, Input Source,
Mux, Speaker

Front and "Mic as Output" are dummy. The other ones work and I can set
different volumes for the headphone and the speaker :-)

If I add the line-in again, the speaker no longer works and the
control names in alsamixer are wrong. Any suggestions?

Thanks,
Rafael

P.S.: I have just remembered to upgrade the alsa libs and utils. I
will send another email if it works.

-------------------------------------------------------------------------
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

Re: trying to get sound working at a mac book pro (core 2 duo)

[Rafael Espíndola]

> P.S.: I have just remembered to upgrade the alsa libs and utils. I
> will send another email if it works.

It doesn't :-(
Same problem with alsa-lib and alsa-utils from hg

Rafael

-------------------------------------------------------------------------
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

Re: trying to get sound working at a mac book pro (core 2 duo)

[Rafael Espíndola]

Looking at the windows ini files I noticed that BOARD3.INI is the most
similar to the macbook pro: has an spdif input (code C) and an
internal microphone.

I am copying the config from BOARD3.INI to the linux driver. Currently
I am using:

static unsigned int macbook_pin_configs[10] = {
       0x0221401f, 0x90a70120, 0x01813024, 0x01014010,
       0x400000fd, 0x01016011, 0x1345e240, 0x13c5e22e,
       0x400000fc, 0x400000fb,
};

This is the best result so far:
*) mic works after switch to line in and back
*) speakers works
*) microphone works
*) microphone sensing works

Cheers,
Rafael

-------------------------------------------------------------------------
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