mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: davidjonx@gmail.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Multiple Codec Problem With Intel HD Audio
Date: Wed, 21 Jul 2010 07:46:07 +0200	[thread overview]
Message-ID: <s5hwrspwfog.wl%tiwai@suse.de> (raw)
In-Reply-To: <4C4672D4.9030400@gmx.com>

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


Takashi

  reply	other threads:[~2010-07-21  5:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-18 16:38 David John
2010-07-19 23:17 ` Takashi Iwai
2010-07-21  4:08   ` David John
2010-07-21  5:46     ` Takashi Iwai [this message]
2010-07-21  5:58       ` David John

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=s5hwrspwfog.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=davidjonx@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®