From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ASoC: dapm: add support to pinctrl dapm
Date: Mon, 5 Mar 2018 20:35:48 +0000 [thread overview]
Message-ID: <21635274-1d7b-5ed9-6832-2e12fd844f7a@linaro.org> (raw)
In-Reply-To: <20180305155208.GK8588@sirena.org.uk>
Thanks for the review,
On 05/03/18 15:52, Mark Brown wrote:
> On Mon, Mar 05, 2018 at 12:32:13PM +0000, srinivas.kandagatla@linaro.org wrote:
>
>> +int dapm_pinctrl_event(struct snd_soc_dapm_widget *w,
>> + struct snd_kcontrol *kcontrol, int event)
>> +{
>> + struct snd_soc_dapm_pinctrl_priv *priv = w->priv;
>> + struct pinctrl *p = w->pinctrl;
>> + struct pinctrl_state *s;
>> +
>> + if (!p || !priv)
>> + return -EIO;
>> +
>> + soc_dapm_async_complete(w->dapm);
>
> This doesn't look right - we're trying to synchronize with the DAPM
> async queue from something that should be run inside that very queue.
> What is this supposed to be doing?
I thought this is supposed to ensure that any pending asynchronous I/O
is completed before touching pinctrl framework.
TBH, I have done this inline with regulators/clk dapm events.
--srini
>
next prev parent reply other threads:[~2018-03-05 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 12:32 srinivas.kandagatla
2018-03-05 15:52 ` Mark Brown
2018-03-05 20:35 ` Srinivas Kandagatla [this message]
2018-03-07 15:13 ` Mark Brown
2018-03-07 16:20 ` Srinivas Kandagatla
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=21635274-1d7b-5ed9-6832-2e12fd844f7a@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®