linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Viswanath L <viswanathl@nvidia.com>
Cc: <perex@perex.cz>, <tiwai@suse.com>, <mkumard@nvidia.com>,
	<jonathanh@nvidia.com>, <arnd@arndb.de>,
	<yung-chuan.liao@linux.intel.com>, <baolin.wang@linaro.org>,
	<kstewart@linuxfoundation.org>, <Julia.Lawall@inria.fr>,
	<tglx@linutronix.de>, <alsa-devel@alsa-project.org>,
	<linux-kernel@vger.kernel.org>, <spujar@nvidia.com>,
	<sharadg@nvidia.com>, <rlokhande@nvidia.com>,
	<DRAMESH@nvidia.com>, <atalambedu@nvidia.com>
Subject: Re: [PATCH] ALSA: hda: Clear RIRB status before reading WP
Date: Thu, 06 Feb 2020 11:47:46 +0100	[thread overview]
Message-ID: <s5hzhdw8019.wl-tiwai@suse.de> (raw)
In-Reply-To: <1580983853-351-1-git-send-email-viswanathl@nvidia.com>

On Thu, 06 Feb 2020 11:10:53 +0100,
Viswanath L wrote:
> 
> From: Mohan Kumar <mkumard@nvidia.com>
> 
> RIRB interrupt status getting cleared after the write pointer is read
> causes a race condition, where last response(s) into RIRB may remain
> unserviced by IRQ, eventually causing azx_rirb_get_response to fall
> back to polling mode. Clearing the RIRB interrupt status ahead of
> write pointer access ensures that this condition is avoided.
> 
> Signed-off-by: Mohan Kumar <mkumard@nvidia.com>
> Signed-off-by: Viswanath L <viswanathl@nvidia.com>

Applied, thanks.


Takashi

      reply	other threads:[~2020-02-06 10:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 10:10 [PATCH] ALSA: hda: Clear RIRB status before reading WP Viswanath L
2020-02-06 10:47 ` 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=s5hzhdw8019.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=DRAMESH@nvidia.com \
    --cc=Julia.Lawall@inria.fr \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnd@arndb.de \
    --cc=atalambedu@nvidia.com \
    --cc=baolin.wang@linaro.org \
    --cc=jonathanh@nvidia.com \
    --cc=kstewart@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkumard@nvidia.com \
    --cc=perex@perex.cz \
    --cc=rlokhande@nvidia.com \
    --cc=sharadg@nvidia.com \
    --cc=spujar@nvidia.com \
    --cc=tglx@linutronix.de \
    --cc=tiwai@suse.com \
    --cc=viswanathl@nvidia.com \
    --cc=yung-chuan.liao@linux.intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).