Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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, 23 Dec 2019 23:14:07 +0100	[thread overview]
Message-ID: <s5heewuwuz4.wl-tiwai@suse.de> (raw)
In-Reply-To: <20191223171833.GA17053@chua>

On Mon, 23 Dec 2019 18:18:33 +0100,
Klaus Ethgen wrote:
> 
> Hi Takashi,
> 
> Am Di den 10. Dez 2019 um 16:19 schrieb Takashi Iwai:
> > Could you try the patch below in addition to the previous one?
> > The similar trick was applied to the recent Intel chips for the
> > unreliable communications, and the same might work for older chips,
> > too.
> 
> This patch seemed to have fixed the issue. I didn't see the problem
> again since.

OK, good to hear.  I believe we should apply this workaround for the
all Intel chips, then.

I'll submit the proper patch now.


thanks,

Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

      reply	other threads:[~2019-12-23 22:15 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
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 [this message]

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=s5heewuwuz4.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox