All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 2/2] ALSA: hda - add sanity check to force the separate stream tags
Date: Wed, 15 Feb 2017 21:25:42 +0100	[thread overview]
Message-ID: <s5hk28rw69l.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170215160943.26504-2-perex@perex.cz>

On Wed, 15 Feb 2017 17:09:43 +0100,
Jaroslav Kysela wrote:
> 
> It seems that newer Intel chipsets have more than 15 I/O streams (total).
> This patch forces the separate stream tags, when this hardware is detected
> to avoid SDxCTL.STRM field overflow and an unexpected behaviour.
> 
> Signed-off-by: Jaroslav Kysela <perex@perex.cz>

It's a good idea.  Applied now.


thanks,

Takashi

  reply	other threads:[~2017-02-15 20:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 16:09 [PATCH 1/2] ALSA: hda - fix Lewisburg audio issue Jaroslav Kysela
2017-02-15 16:09 ` [PATCH 2/2] ALSA: hda - add sanity check to force the separate stream tags Jaroslav Kysela
2017-02-15 20:25   ` Takashi Iwai [this message]
2017-02-15 20:25 ` [PATCH 1/2] ALSA: hda - fix Lewisburg audio issue 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=s5hk28rw69l.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=perex@perex.cz \
    /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.