Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp8560805pxu; Sun, 27 Dec 2020 10:48:53 -0800 (PST) X-Google-Smtp-Source: ABdhPJyNrgzcuLrn7m6rNunf1UJ3OXpewC2obj4nbULWuuCi1cYrt/tHonBMLAqemCRAseTGQbgo X-Received: by 2002:a50:e845:: with SMTP id k5mr5686790edn.35.1609094933212; Sun, 27 Dec 2020 10:48:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1609094933; cv=none; d=google.com; s=arc-20160816; b=l2hu3uS18vtVfaq9tawVKFFyjin/LJuoaF4JLLMv2bQMrnrxSHKypN93Joda24bccr 9kovI+tsQAyXh/rgEsx5wD7jWE+4neK1al8TDuLUfOWeMNLnqBVfDK0c3di8Yg3xM6ac k3ldDMHUm7rWEgJFDyXuBUFA8szfRvhZxJYipuid8TITHZkk1gJhzPstuX7TLojm/pNN id0exm0OTAbS6rjNRBK/rARpA4Un7U2OXTnVkKYGLSS4K215/CWyjRHCBhHa1QpMToRY 5kZFAQNpHFzYijGaFqDnAw9Y7Rs19VjF59dDdjTQlfLceiTzpHxogzuiOj060ohfg82m GHsA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:in-reply-to :subject:cc:to:from:message-id:date; bh=D0zAC5cx2ZfzIkJUeCmVnVaeJjTHWCVeuIKPn0zo4iE=; b=S9CzcSsX18ugxgRaNWWtd8JMOBlrAaKhHHnvIqcFDZ8FI8DzWp/3hA0YcTAbPrbwoL kf5PjnDvpL6i0IF0MZxJaZjKB0jzJhfS+XJPWLZsHFx5AuREpg7ID1bbWiGjqq5Ix6Xf cLPXVEZ+NhEY03hR/inpM7aJQYlCxsD9wACdspOzgn/pVm7jAR/k9qdgOPts+Izj7efL 57e0hIZXiKgSNg0ZrvDNmMYVnYPVp9zh+3FLsZhbvPPeoWDnrV04gFfLeq1Ar8bXJkMl C/y+IBwfV30R/g1lMJTrmDU86Rr0+lqKRp6O/SctwXwLSZeg2HGw1r4ONhP1yJTBAsuW QJHA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i5si19524246edv.542.2020.12.27.10.48.31; Sun, 27 Dec 2020 10:48:53 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726116AbgL0SrI (ORCPT + 99 others); Sun, 27 Dec 2020 13:47:08 -0500 Received: from mx2.suse.de ([195.135.220.15]:52214 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725945AbgL0SrI (ORCPT ); Sun, 27 Dec 2020 13:47:08 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id A6866AC37; Sun, 27 Dec 2020 18:46:26 +0000 (UTC) Date: Sun, 27 Dec 2020 19:46:26 +0100 Message-ID: From: Takashi Iwai To: Jaroslav Kysela Cc: Ravulapati Vishnu vardhan rao , Alexander.Deucher@amd.com, Liam Girdwood , Mark Brown , Takashi Iwai , Akshu Agrawal , Dan Carpenter , Vijendar Mukunda , "moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..." , open list Subject: Re: [PATCH] ASoC: amd:Replacing MSI with Legacy IRQ model In-Reply-To: <9f1df5a9-f2ab-33da-3111-c01db88912b4@perex.cz> References: <20201222115929.11222-1-Vishnuvardhanrao.Ravulapati@amd.com> <9f1df5a9-f2ab-33da-3111-c01db88912b4@perex.cz> 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 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 27 Dec 2020 19:03:28 +0100, Jaroslav Kysela wrote: > > Dne 22. 12. 20 v 12:59 Ravulapati Vishnu vardhan rao napsal(a): > > When we try to play and capture simultaneously we see that > > interrupts are genrated but our handler is not being acknowledged, > > After investigating further more in detail on this issue we found > > that IRQ delivery via MSI from the ACP IP is unreliable and so sometimes > > interrupt generated will not be acknowledged so MSI model shouldn't be used > > and using legacy IRQs will resolve interrupt handling issue. > > What is the real culprit? It's hw bug? If not, it would be better to fix the > PCI code or the irq handler. I'm not surprised if it's a hardware "feature". There are lots of deny list and quirks about disabling MSI in HD-audio controller code, after all. Takashi