From: Takashi Iwai <tiwai@suse.de>
To: Klaus Ethgen <Klaus@ethgen.ch>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] CPU hook snd_hda_intel
Date: Mon, 09 Dec 2019 10:27:23 +0100 [thread overview]
Message-ID: <s5h4ky9hmro.wl-tiwai@suse.de> (raw)
In-Reply-To: <20191209085716.GA12935@ikki.ethgen.ch>
On Mon, 09 Dec 2019 09:57:16 +0100,
Klaus Ethgen wrote:
>
> Hi Takashi,
>
> Am Mo den 9. Dez 2019 um 8:10 schrieb Takashi Iwai:
> > > I hardly have such new Architectures on that laptop. It is a lenovo x61s
> > > so it is from latest 2009. It has a Intel Core 2 Duo LV (Merom). :-)
> >
> > OK, then could you give alsa-info.sh output, at least?
> > Run the script with --no-upload option and attach the output.
>
> Sure. See attached output.
Thanks!
Maybe unrelated with this particular problem, but I wonder why you
didn't enable CONFIG_SND_HDA_CODEC_ANALOG. You're using the generic
codec driver and it misses a few vendor-specific fixes / workarounds.
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-12-09 9:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 18:47 [alsa-devel] CPU hook snd_hda_intel Klaus Ethgen
2019-12-04 16:31 ` Takashi Iwai
2019-12-07 20:06 ` Klaus Ethgen
2019-12-08 8:45 ` Takashi Iwai
2019-12-08 17:31 ` Klaus Ethgen
2019-12-09 7:10 ` Takashi Iwai
2019-12-09 8:57 ` Klaus Ethgen
2019-12-09 9:27 ` Takashi Iwai [this message]
2019-12-09 9:45 ` Klaus Ethgen
2019-12-10 14:32 ` Klaus Ethgen
2019-12-10 14:35 ` Klaus Ethgen
2019-12-10 14:43 ` Takashi Iwai
2019-12-10 15:10 ` Klaus Ethgen
2019-12-10 15:19 ` Takashi Iwai
2019-12-10 15:28 ` Klaus Ethgen
2019-12-23 17:18 ` Klaus Ethgen
2019-12-23 22:14 ` 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=s5h4ky9hmro.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Klaus@ethgen.ch \
--cc=alsa-devel@alsa-project.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 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.