From: Takashi Iwai <tiwai@suse.de>
To: Francis Moreau <francis.moro@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: 3.1-rc5 is the worst
Date: Tue, 13 Sep 2011 10:39:11 +0200 [thread overview]
Message-ID: <s5hmxe8vntc.wl%tiwai@suse.de> (raw)
In-Reply-To: <CAC9WiBhng3Aa9N+GM-ND100jqb+x22wAp+c9rTDEJ2riKtNZ7w@mail.gmail.com>
At Mon, 12 Sep 2011 16:25:44 +0200,
Francis Moreau wrote:
>
> On Mon, Sep 12, 2011 at 3:14 PM, Francis Moreau <francis.moro@gmail.com> wrote:
> > Hello,
> >
> > On Mon, Sep 12, 2011 at 11:24 AM, Takashi Iwai <tiwai@suse.de> wrote:
> >> At Sat, 10 Sep 2011 11:57:06 +0200,
> >> Francis Moreau wrote:
> >>>
> >>> Hello,
> >>>
> >>> Maybe the subject sounds rude so apologize since I just want to report
> >>> that 3.1-rc5 gives me bad impression.
> >>>
> >>> Of course it's all about my hw support which seems to get some
> >>> regressions (I attached lspci).
> >>>
> >>> 1/ I'm getting this now at each boot:
> >>>
> >>> [ 38.349671] hda_codec: too deep connection for 0x18
> >>> [ 38.349748] hda_codec: too deep connection for 0x18
> >>> [ 38.349842] hda_codec: too deep connection for 0x18
> >>> [ 38.349843] hda_codec: too deep connection for 0x18
> >>> [ 38.349844] hda_codec: too deep connection for 0x18
> >>> [ 38.349939] hda_codec: too deep connection for 0x18
> >>> <repeated 252 times>
> >>>
> >>> I've no idea what it does mean or it's simply a warning I can ignore
> >>> (and it that case it would be nice to limit it at least) or if it's
> >>> worse getting a fix before 3.1 is out would be great.
> >>
> >> Could you give alsa-info.sh outputs (run with --no-upload option)
> >> for both working and non-working kernels? lspci doesn't expose
> >> anything about codecs and other details.
> >>
> >
> > Here is the output from the working kernel (no "too deep connection
> > ..." warnings). kernel is 2.6.39.4.
> >
> > I can't give the output for the non-working kernel since I can't
> > reboot right now. I'll send it later.
> >
>
> Ok here's the output for the bad one.
>
> Let me know if you want something else.
Thanks!
The patch below should fix the problem. Give it a try.
Takashi
---
From: Takashi Iwai <tiwai@suse.de>
Subject: [PATCH] ALSA: hda - Terminate the recursive connection search properly
The recursive search of widget connections in snd_hda_get_conn_index()
must be terminated at the pin and the audio-out widgets. Otherwise
you'll get "too deep connection" warnings unnecessarily.
Signed-off-by: Takashi Iwai <tiwai@suse.de>
---
sound/pci/hda/hda_codec.c | 6 +++++-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/sound/pci/hda/hda_codec.c b/sound/pci/hda/hda_codec.c
index 3e7850c..f3aefef 100644
--- a/sound/pci/hda/hda_codec.c
+++ b/sound/pci/hda/hda_codec.c
@@ -579,9 +579,13 @@ int snd_hda_get_conn_index(struct hda_codec *codec, hda_nid_t mux,
return -1;
}
recursive++;
- for (i = 0; i < nums; i++)
+ for (i = 0; i < nums; i++) {
+ unsigned int type = get_wcaps_type(get_wcaps(codec, conn[i]));
+ if (type == AC_WID_PIN || type == AC_WID_AUD_OUT)
+ continue;
if (snd_hda_get_conn_index(codec, conn[i], nid, recursive) >= 0)
return i;
+ }
return -1;
}
EXPORT_SYMBOL_HDA(snd_hda_get_conn_index);
--
1.7.6.1
next prev parent reply other threads:[~2011-09-13 8:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 9:57 Francis Moreau
2011-09-10 15:11 ` Keith Packard
2011-09-10 19:42 ` Francis Moreau
2011-09-11 7:09 ` Sitsofe Wheeler
2011-09-11 18:32 ` Francis Moreau
2011-09-11 18:33 ` Francis Moreau
2011-09-20 17:18 ` Keith Packard
2011-09-20 20:55 ` Francis Moreau
2011-09-21 7:57 ` Francis Moreau
2011-09-21 14:47 ` Keith Packard
2011-09-21 18:56 ` Hugh Dickins
2011-09-21 19:16 ` Keith Packard
2011-09-12 9:05 ` Clemens Ladisch
2011-09-12 9:24 ` Takashi Iwai
2011-09-12 13:14 ` Francis Moreau
2011-09-12 14:25 ` Francis Moreau
2011-09-13 8:39 ` Takashi Iwai [this message]
2011-09-14 7:03 ` Francis Moreau
2011-09-15 20:00 ` Linus Torvalds
2011-09-16 4:56 ` 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=s5hmxe8vntc.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=francis.moro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®