All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérémy Lal" <kapouer@melix.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
	Rafael Avila de Espindola <rafael.espindola@gmail.com>
Subject: Re: iMac12,2 cirrus_patch.c model detection
Date: Sun, 15 May 2011 21:26:57 +0200	[thread overview]
Message-ID: <4DD02901.20607@melix.org> (raw)
In-Reply-To: <s5h8vu847dh.wl%tiwai@suse.de>

On 15/05/2011 11:53, Takashi Iwai wrote:
> At Sun, 15 May 2011 10:20:10 +0200,
> Jérémy Lal wrote:
>>
>> 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
>>
>> 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.
> 
> 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.

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

> 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
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

       reply	other threads:[~2011-05-15 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4DCF8CBA.8070902@melix.org>
     [not found] ` <s5h8vu847dh.wl%tiwai@suse.de>
2011-05-15 19:26   ` Jérémy Lal [this message]
2011-05-16  8:26     ` iMac12,2 cirrus_patch.c model detection 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=4DD02901.20607@melix.org \
    --to=kapouer@melix.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=rafael.espindola@gmail.com \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.