[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191001172941.GC4786@sirena.co.uk>
Date: Tue, 1 Oct 2019 18:29:41 +0100
From: Mark Brown <broonie@...nel.org>
To: "Deucher, Alexander" <Alexander.Deucher@....com>
Cc: "RAVULAPATI, VISHNU VARDHAN RAO"
<Vishnuvardhanrao.Ravulapati@....com>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
"Mukunda, Vijendar" <Vijendar.Mukunda@....com>,
Maruthi Srinivas Bayyavarapu <Maruthi.Bayyavarapu@....com>,
Colin Ian King <colin.king@...onical.com>,
Dan Carpenter <dan.carpenter@...cle.com>,
"moderated list:SOUND - SOC LAYER / DYNAMIC AUDIO POWER MANAGEM..."
<alsa-devel@...a-project.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/7] ASoC: amd: No need PCI-MSI interrupts
On Tue, Oct 01, 2019 at 05:23:43PM +0000, Deucher, Alexander wrote:
> > ACP-PCI controller driver does not depends msi interrupts.
> > So removed msi related pci functions which have no use and does not impact
> > on existing functionality.
> In general, however, aren't MSIs preferred to legacy interrupts?
As I understand it. Or at the very least I'm not aware of any situation
where they're harmful. It'd be good to have a clear explanation of why
we're removing the support.
> Doesn't the driver have to opt into MSI support? As such, won't
> removing this code effectively disable MSI support?
Yes.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists