From: Jarkko Nikula <jhnikula@gmail.com>
To: "Candelaria Villareal, Jorge" <jorge.candelaria@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCHv2 6/6] ASoC: OMAP4: Add McPDM platform driver
Date: Tue, 26 Jan 2010 10:27:48 +0200 [thread overview]
Message-ID: <20100126102748.3b9fb04d.jhnikula@gmail.com> (raw)
In-Reply-To: <2256F256009DAA4CBE661E9F41EAC84B8C4CEF36@dlee01.ent.ti.com>
Hi
On Mon, 25 Jan 2010 15:06:44 -0600
"Candelaria Villareal, Jorge" <jorge.candelaria@ti.com> wrote:
> > > +static int omap_mcpdm_dai_startup(struct snd_pcm_substream
> > *substream,
> > > + struct snd_soc_dai *dai)
> > > +{
> > > + struct snd_soc_pcm_runtime *rtd = substream->private_data;
> > > + struct snd_soc_dai *cpu_dai = rtd->dai->cpu_dai;
> > > + int err = 0;
> > > +
> > > + if (!cpu_dai->active)
> > > + err = omap_mcpdm_request();
> >
> > Will anything else use this hw interface other than ALSA audio ?
> > If not, the request is probably better in the machine driver probe().
>
> omap_mcpdm_request will enable the functional clock. Isn't it better
> for the clock to be enabled only when is about to get used?
>
Definitely yes if there is no any need to keep block active after the
request. That would help the power-management if there are no active
clocks when the streams are suspended with omap_mcpdm_stop() but the
block remains reserved (i.e. omap_mcpdm_free is not called).
The current McBSP implementation is not the best example here but
hopefully that will get fixed at some point.
> > stream is either PLAYBACK or CAPTURE here.
>
> Downlink and uplink were chosen instead to avoid confusion
> because that is how it is referred in McPDM technical
> documentation. But I do understand that we are talking
> about ALSA stream, not McPDM...
...
> Here, however, the methods set_uplink & set_downlink are
> Named after McPDM data paths. In this case is it preferred
> to name everything using ALSA convention? Or would it be ok
> to use downlink/uplink on certain cases?
>
I think something like below is clear enough. It is easy to see that we
are dealing with ALSA playback stream which corresponds to downlink path
in HW.
if (stream == SNDRV_PCM_STREAM_PLAYBACK)
omap_mcpdm_downlink_opxxx();
Also for the user(-space) standard playback and capture naming is more
clear than downlink/uplink terminology.
--
Jarkko
next prev parent reply other threads:[~2010-01-26 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 23:15 [PATCHv2 6/6] ASoC: OMAP4: Add McPDM platform driver Candelaria Villareal, Jorge
2010-01-23 1:37 ` Liam Girdwood
2010-01-25 21:06 ` [alsa-devel] " Candelaria Villareal, Jorge
2010-01-26 8:27 ` Jarkko Nikula [this message]
2010-01-26 10:30 ` Liam Girdwood
2010-01-26 17:55 ` Candelaria Villareal, Jorge
2010-01-26 10:33 ` Liam Girdwood
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=20100126102748.3b9fb04d.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jorge.candelaria@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
/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).