From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1762199Ab0GUF6P (ORCPT <rfc822;w@1wt.eu>);
	Wed, 21 Jul 2010 01:58:15 -0400
Received: from mailout-us.gmx.com ([74.208.5.67]:60426 "HELO
	mailout-us.gmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with SMTP id S1753156Ab0GUF6I (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 21 Jul 2010 01:58:08 -0400
X-Authenticated: #61118693
X-Provags-ID: V01U2FsdGVkX1+8hXs+pTm89dtHvKX7eODVFZzL/31f8v9gZZuSme
	UQDFzAp2/QQVeE
Message-ID: <4C468C7A.3070302@gmx.com>
Date: Wed, 21 Jul 2010 11:28:18 +0530
From: David John <davidjon@gmx.com>
Reply-To: davidjon@gmx.com
User-Agent: Mozilla/5.0 (X11; X; Linux x86_64; rv:1.9.1.9) Gecko/20100430 Thunderbird/3.0.4
MIME-Version: 1.0
To: Takashi Iwai <tiwai@suse.de>
CC: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Multiple Codec Problem With Intel HD Audio
References: <4C432E1D.3000703@gmx.com>	<s5hwrsrxdrx.wl%tiwai@suse.de>	<4C4672D4.9030400@gmx.com> <s5hwrspwfog.wl%tiwai@suse.de>
In-Reply-To: <s5hwrspwfog.wl%tiwai@suse.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 07/21/2010 11:16 AM, Takashi Iwai wrote:
> At Wed, 21 Jul 2010 09:38:52 +0530,
> David John wrote:
>>
>>> Yes, this looks like the issue.
>>>
>>> A possible fix without much hustle would be to define mode quirks for
>>> both codecs by checking the PCI SSID so that they won't conflict.
>>
>> How would I go about doing this as the dmesg dump had the following:
>>
>>> ALSA sound/pci/hda/patch_realtek.c:1287: realtek: *No valid SSID*,
>>> checking pincfg 0x40000001 for NID 0x1d
>>> ALSA sound/pci/hda/patch_realtek.c:1303: realtek: Enabling init
>>> ASM_ID=0x0001 CODEC_ID=10ec0888
> 
> The SSID in the above is the codec SSID.  That can be different from
> PCI SSID although they are identical in many cases.
> 
> Realtek codecs suppose that the codec SSID is set to represent the
> hardware implementation status so that the driver can initialize
> based on it.  The message above shows that your machine doesn't
> provide such SSID (as many vendors don't follow that policy,
> obviously).
> 

Ah, okay.

Thanks,
David.