From: Mark Brown <broonie@kernel.org>
To: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
Cc: "Péter Ujfalusi" <peter.ujfalusi@gmail.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,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Ranjani Sridharan" <ranjani.sridharan@linux.intel.com>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ASoC: dwc: add a quirk DW_I2S_QUIRK_STOP_ON_SHUTDOWN to dwc driver
Date: Thu, 13 May 2021 15:05:56 +0100 [thread overview]
Message-ID: <20210513140556.GD5813@sirena.org.uk> (raw)
In-Reply-To: <9b689495-e956-6242-0784-af3ccf7c3238@amd.com>
[-- Attachment #1: Type: text/plain, Size: 371 bytes --]
On Mon, May 10, 2021 at 10:57:25PM +0530, Mukunda,Vijendar wrote:
> How about declaring a flag in sound card structure and this flag will be set
> in stoneyridge machine driver.
> Based on flag check trigger stop sequence will be re-ordered.
A couple of people suggested that already, making sure the core knows
what's going on is probably the best way forwards here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-05-13 14:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 16:24 [PATCH 1/2] ASoC: dwc: add a quirk DW_I2S_QUIRK_STOP_ON_SHUTDOWN to dwc driver Vijendar Mukunda
2021-04-23 16:24 ` [PATCH 2/2] drm/amd/amdgpu: Add dwc quirk for Stoney/CZ platforms Vijendar Mukunda
2021-04-23 16:46 ` [PATCH 1/2] ASoC: dwc: add a quirk DW_I2S_QUIRK_STOP_ON_SHUTDOWN to dwc driver Mark Brown
2021-04-26 6:19 ` Péter Ujfalusi
2021-04-26 12:21 ` Mukunda,Vijendar
2021-04-27 6:40 ` Péter Ujfalusi
2021-04-28 15:35 ` Mukunda,Vijendar
2021-04-30 5:42 ` Péter Ujfalusi
2021-04-30 18:35 ` Mukunda,Vijendar
2021-05-10 17:27 ` Mukunda,Vijendar
2021-05-13 14:05 ` Mark Brown [this message]
2021-05-17 8:07 ` Péter Ujfalusi
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=20210513140556.GD5813@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=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@gmail.com \
--cc=ranjani.sridharan@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).