From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ola Lilja <ola.o.lilja@stericsson.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 03/11] ASoC: core: Add widget SND_SOC_DAPM_CLOCK_SUPPLY
Date: Tue, 8 May 2012 16:40:28 +0100 [thread overview]
Message-ID: <20120508154027.GY15893@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1336485400-27150-1-git-send-email-ola.o.lilja@stericsson.com>
[-- Attachment #1.1: Type: text/plain, Size: 1118 bytes --]
On Tue, May 08, 2012 at 03:56:40PM +0200, Ola Lilja wrote:
> +{
> + if (SND_SOC_DAPM_EVENT_ON(event))
> + return clk_enable(w->priv);
> + else {
> + clk_disable(w->priv);
> + return 0;
Coding style - you need more { }. This also all needs to be
conditionally complied for the many platforms that don't provide the
clock API.
> + case snd_soc_dapm_clock_supply:
> + w->priv = (w->shift) ? clk_get_sys(w->name, NULL) :
> + clk_get(dapm->dev, w->name);
I don't think supporting clk_get_sys() is a particularly good idea
here... Also, I think Liam was wanting to add per-user data to the
widget rather than reuse the priv pointer.
> + /**
> + * snd_soc_dapm_get_power_status - get widget power status
> + * @dapm: DAPM context
> + * @pin: Widget name
> + *
> + * Get widget power status - Enabled or disabled.
> + *
> + * Returns -1 for failure.
> + * Returns 0 if disabled.
> + * Returns 1 if enabled.
> + */
> +int snd_soc_dapm_get_power_status(struct snd_soc_dapm_context *dapm,
> + const char *pin)
This appears to be *nothing* to do with the rest of the patch! It's
also not clear what it's for.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-05-08 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 13:56 [PATCH 03/11] ASoC: core: Add widget SND_SOC_DAPM_CLOCK_SUPPLY Ola Lilja
2012-05-08 15:40 ` Mark Brown [this message]
2012-05-09 7:55 ` Ola Lilja
2012-05-09 8:47 ` Mark Brown
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=20120508154027.GY15893@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linus.walleij@linaro.org \
--cc=lrg@ti.com \
--cc=ola.o.lilja@stericsson.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).