[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <07047388-6570-6501-abfd-f940777ad5cc@amd.com>
Date: Wed, 7 Jul 2021 15:55:31 +0530
From: "Mukunda,Vijendar" <vijendar.mukunda@....com>
To: Mark Brown <broonie@...nel.org>
Cc: peter.ujfalusi@...com, alsa-devel@...a-project.org,
amistry@...gle.com, nartemiev@...gle.com,
Alexander.Deucher@....com, Basavaraj.Hiregoudar@....com,
Sunil-kumar.Dommati@....com, Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Chuhong Yuan <hslester96@...il.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] ASoC: add stop_dma_first flag to reverse the stop
sequence
On 7/6/21 5:58 PM, Mark Brown wrote:
> On Tue, Jul 06, 2021 at 01:06:17AM +0530, Vijendar Mukunda wrote:
>
>> @@ -982,6 +982,7 @@ struct snd_soc_card {
>> unsigned int disable_route_checks:1;
>> unsigned int probed:1;
>> unsigned int component_chaining:1;
>> + unsigned int stop_dma_first:1;
>>
>> void *drvdata;
>> };
>
> This still doesn't seem like something which should be controlled at the
> card level, I'd expect it to be configured at the dai_link level.
>
will make changes by adding flag in dai_link and will post the new version
Powered by blists - more mailing lists