From: Mark Brown <broonie@kernel.org>
To: Vijendar Mukunda <vijendar.mukunda@amd.com>
Cc: peter.ujfalusi@ti.com, alsa-devel@alsa-project.org,
amistry@google.com, nartemiev@google.com,
Alexander.Deucher@amd.com, Basavaraj.Hiregoudar@amd.com,
Sunil-kumar.Dommati@amd.com, Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Chuhong Yuan <hslester96@gmail.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ASoC: add stop_dma_first flag to reverse the stop sequence
Date: Tue, 6 Jul 2021 13:28:44 +0100 [thread overview]
Message-ID: <20210706122844.GD4529@sirena.org.uk> (raw)
In-Reply-To: <20210705193620.1144-1-vijendar.mukunda@amd.com>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-07-06 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 19:36 [PATCH v2] ASoC: add stop_dma_first flag to reverse the stop sequence Vijendar Mukunda
2021-07-06 12:28 ` Mark Brown [this message]
2021-07-07 10:25 ` Mukunda,Vijendar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210706122844.GD4529@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Alexander.Deucher@amd.com \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=amistry@google.com \
--cc=hslester96@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nartemiev@google.com \
--cc=perex@perex.cz \
--cc=peter.ujfalusi@ti.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.com \
--cc=vijendar.mukunda@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).