Skip to contentSkip to conversation

iMac12,2 cirrus_patch.c model detection

DISCUSSION Jérémy Lal 2 participants 2 messages May 15, 2011 – May 16, 2011 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): s5h8vu847dh.wl%[email protected]

#2 lore raw
Quoted 15 lines · Takashi Iwai

At Sun, 15 May 2011 10:20:10 +0200,

Quoted 7 lines · Jérémy Lal

Hi,
the imac12,2 27" (model name iMac12,2 from may 2011),
has some headphones bug with your latest patch (the one that adds model=imac27). More precisions at :
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5364

Quoted 5 lines

I cooked a dirty patch (that fixes all controls that i can test, that is all analog in/out) and attached it in that bug report. However, since lspci reports subsystem 0x8086, 0x7270 too,
i can't make that model auto-detected without killing your imac27 patch, see bug report.

Quoted 6 lines

The bug tracking system is almost broken and actually no developer is using it. I proposed to shut it down many times, but it's still present, unfortunately.

Could you post your results to alsa-devel ML and continue discussing there?

cc-ing alsa-devel, then.

Quoted 6 lines
Quoted 1 line

Would you have some advice to make it properly detect "my" model ?

Create a table of codec SSID (not PCI SSID) and check the model via snd_hda_check_board_codec_sid_config() first, then use snd_hda_check_board_config() when no matching entry is found, as fallback.

That makes sense, and i'll use patch_realtek.c as an example. I'm inexperimented in C or alsa, though, so i might fail doing this.

Quoted 2 lines

Of course, this assumes that the codec SSID is unique. Hopefully Apple does something right, at least.

I don't get what you mean. Anyway bootcamp ships with the cirrus driver for windows, which lists all vendor/dev/subsys supported ids, with all configurations for pins, gpio, and other stuff i don't understand. It's tempting to use that to cover all actual models...
I'd need to get a minimal knowledge of how intel hda and associated chips like cirrus work together. Any advice, beginner's guide ?

Jérémy Lal

_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

#3 lore raw

At Sun, 15 May 2011 21:26:57 +0200,

Quoted 28 lines · Jérémy Lal
Quoted 15 lines · Takashi Iwai

At Sun, 15 May 2011 10:20:10 +0200,

Quoted 7 lines · Jérémy Lal

Hi,
the imac12,2 27" (model name iMac12,2 from may 2011),
has some headphones bug with your latest patch (the one that adds model=imac27). More precisions at :
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5364

Quoted 5 lines

I cooked a dirty patch (that fixes all controls that i can test, that is all analog in/out) and attached it in that bug report. However, since lspci reports subsystem 0x8086, 0x7270 too,
i can't make that model auto-detected without killing your imac27 patch, see bug report.

Quoted 6 lines

The bug tracking system is almost broken and actually no developer is using it. I proposed to shut it down many times, but it's still present, unfortunately.

Could you post your results to alsa-devel ML and continue discussing there?

cc-ing alsa-devel, then.

Quoted 2 lines
Quoted 1 line

Would you have some advice to make it properly detect "my" model ?

Quoted 7 lines
Quoted 4 lines

Create a table of codec SSID (not PCI SSID) and check the model via snd_hda_check_board_codec_sid_config() first, then use snd_hda_check_board_config() when no matching entry is found, as fallback.

That makes sense, and i'll use patch_realtek.c as an example. I'm inexperimented in C or alsa, though, so i might fail doing this.

Don't worry, just send your patch, and we'll check it ;)

Quoted 4 lines
Quoted 2 lines

Of course, this assumes that the codec SSID is unique. Hopefully Apple does something right, at least.

I don't get what you mean.

Well, you know, Apple doesn't set the right pin-config values or whatever in BIOS level at all while other vendors do that correctly in BIOS nowadays. I suspect it's Apple's intentional behavior to hinder other OS :)

Quoted 6 lines

Anyway bootcamp ships with the cirrus driver
for windows, which lists all vendor/dev/subsys supported ids, with all configurations for pins, gpio, and other stuff i don't understand. It's tempting to use that to cover all actual models...
I'd need to get a minimal knowledge of how intel hda and associated chips like cirrus work together. Any advice, beginner's guide ?

The pin-configurations can be re-used almost as is. And it can be changed even dynamically. See Documentation/sound/alsa/HD-Audio.txt.

GPIO setup is more or less dependent on the codec chip and its driver implementation. So for the latter, check the datasheet of the chip. I guess it should be available somewhere in the net.

thanks,

Takashi
_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel