From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=za8s=32=vger.kernel.org=linux-kernel-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS,
	MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED
	autolearn=no autolearn_force=no version=3.4.0
Received: from mail.kernel.org (mail.kernel.org [198.145.29.99])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 2578EC2D0B1
	for <linux-kernel@archiver.kernel.org>; Thu,  6 Feb 2020 10:47:53 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [209.132.180.67])
	by mail.kernel.org (Postfix) with ESMTP id 02D0A227BF
	for <linux-kernel@archiver.kernel.org>; Thu,  6 Feb 2020 10:47:53 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1728428AbgBFKrw (ORCPT
        <rfc822;linux-kernel@archiver.kernel.org>);
        Thu, 6 Feb 2020 05:47:52 -0500
Received: from mx2.suse.de ([195.135.220.15]:47982 "EHLO mx2.suse.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1728319AbgBFKrt (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 6 Feb 2020 05:47:49 -0500
X-Virus-Scanned: by amavisd-new at test-mx.suse.de
Received: from relay2.suse.de (unknown [195.135.220.254])
        by mx2.suse.de (Postfix) with ESMTP id 2B9E1AC4B;
        Thu,  6 Feb 2020 10:47:47 +0000 (UTC)
Date:   Thu, 06 Feb 2020 11:47:46 +0100
Message-ID: <s5hzhdw8019.wl-tiwai@suse.de>
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
In-Reply-To: <1580983853-351-1-git-send-email-viswanathl@nvidia.com>
References: <1580983853-351-1-git-send-email-viswanathl@nvidia.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3
 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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