[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <76668467-5edf-407a-a063-50f322fe785d@amd.com>
Date: Thu, 17 Oct 2019 09:33:06 +0000
From: vishnu <vravulap@....com>
To: Mark Brown <broonie@...nel.org>,
"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 11/10/19 3:03 AM, vishnu wrote:
> Hi,
> Please find my inline comments.
>
> Thanks,
> Vishnu
>
> On 01/10/19 10:59 PM, Mark Brown wrote:
>> 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.
>
> Actually our device is audio device and it does not depends on MSI`s.
> So we thought to remove it as it has no purpose or meaning to have
> this code in our audio based ACP-PCI driver.
>
>>> Doesn't the driver have to opt into MSI support? As such, won't
>>> removing this code effectively disable MSI support?
>>
>> Yes.
>
>
Hi Mark,
Any updates on this patch.
Regards,
Vishnu
Powered by blists - more mailing lists