From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: noman pouigt <variksla@gmail.com>
Cc: Vinod Koul <vinod.koul@linux.intel.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Mark Brown <broonie@kernel.org>,
alsa-devel@alsa-project.org,
pierre-louis.bossart@linux.intel.com
Subject: Re: compress: dpcm_path_get called in wrong place
Date: Fri, 07 Mar 2014 18:28:59 +0000 [thread overview]
Message-ID: <1394216939.2419.37.camel@loki> (raw)
In-Reply-To: <CAES_P+9RrhOGip61Lyb-fq2JgrHZGhifLtoY=LY6_jwbEoJnAA@mail.gmail.com>
On Thu, 2014-03-06 at 23:52 -0800, noman pouigt wrote:
> Shouldn't dpcm_path_get be called earlier ? I think it should be
> called earlier as happens in soc-pcm file.
>
> static int soc_compr_open_fe(struct snd_compr_stream *cstream)
> {
>
> if (dpcm_path_get(fe, stream, &list) <= 0) {
> dev_dbg(fe->dev, "ASoC: %s no valid %s route\n",
> fe->dai_link->name, stream ? "capture" : "playback");
>
> In current code we open platform driver and then machine startup function
> gets called. After this we check for valid path which i think should happen
> earlier i.e. in the beginning of soc_compr_open_fe function.
>
> If you agree, then i will send a patch.
I don't think it's making any difference atm, but for consistency with
dpcm_fe_dai_open() we could re-order. Fwiw, the open functions don't use
any data from the path check yet, but I suppose they could in the
future. Please submit a patch and also CC Mark Brown with your patch.
Thanks
Liam
prev parent reply other threads:[~2014-03-07 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 7:52 compress: dpcm_path_get called in wrong place noman pouigt
2014-03-07 18:28 ` Liam Girdwood [this message]
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=1394216939.2419.37.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=variksla@gmail.com \
--cc=vinod.koul@linux.intel.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