From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>, broonie@kernel.org
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, tiwai@suse.com,
quic_srivasam@quicinc.com
Subject: Re: [PATCH v4] ASoC: codecs: wsa881x: add runtime pm support
Date: Wed, 20 Apr 2022 12:59:12 -0500 [thread overview]
Message-ID: <b1b0a8b9-5fc2-bfe1-dfde-692a0a7ac34a@linux.intel.com> (raw)
In-Reply-To: <20220228144235.24208-1-srinivas.kandagatla@linaro.org>
Hi Srini,
> +static int __maybe_unused wsa881x_runtime_resume(struct device *dev)
> +{
> + struct sdw_slave *slave = dev_to_sdw_dev(dev);
> + struct regmap *regmap = dev_get_regmap(dev, NULL);
> + struct wsa881x_priv *wsa881x = dev_get_drvdata(dev);
> +
> + gpiod_direction_output(wsa881x->sd_n, 1);
> +
> + wait_for_completion_timeout(&slave->initialization_complete,
> + msecs_to_jiffies(WSA881X_PROBE_TIMEOUT));
while I was revisiting pm_runtime support, I also saw that this codec driver is the only one that doesn't check for errors
max98373-sdw.c: time = wait_for_completion_timeout(&slave->initialization_complete,
rt1308-sdw.c: time = wait_for_completion_timeout(&slave->initialization_complete,
rt1316-sdw.c: time = wait_for_completion_timeout(&slave->initialization_complete,
rt5682-sdw.c: time = wait_for_completion_timeout(&slave->initialization_complete,
rt5682.c: &slave->initialization_complete,
rt700-sdw.c: time = wait_for_completion_timeout(&slave->initialization_complete,
rt711-sdca-sdw.c: time = wait_for_completion_timeout(&slave->initialization_complete,
rt711-sdw.c: time = wait_for_completion_timeout(&slave->initialization_complete,
rt715-sdw.c: time = wait_for_completion_timeout(&slave->initialization_complete,
wsa881x.c: wait_for_completion_timeout(&slave->initialization_complete,
If the attachment fails for some reason, you probably want to avoid starting regmap syncs that will fail by construction, no?
> +
> + regcache_cache_only(regmap, false);
> + regcache_sync(regmap);
> +
> + return 0;
> +}
next prev parent reply other threads:[~2022-04-20 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 14:42 Srinivas Kandagatla
2022-02-28 22:23 ` Mark Brown
2022-04-20 17:59 ` Pierre-Louis Bossart [this message]
2022-04-21 9:31 ` 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=b1b0a8b9-5fc2-bfe1-dfde-692a0a7ac34a@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_srivasam@quicinc.com \
--cc=srinivas.kandagatla@linaro.org \
--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®