From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Zhang, Vivian" <vivian.zhang@intel.com>,
"ramesh.babu@intel.com" <ramesh.babu@intel.com>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>
Subject: Re: [PATCH v2 1/2] ASoC: soc-compress: add a config item for soc-compress
Date: Wed, 17 Jun 2015 21:52:56 +0530 [thread overview]
Message-ID: <20150617162256.GE28601@localhost> (raw)
In-Reply-To: <20150617122340.GC3214@sirena.org.uk>
On Wed, Jun 17, 2015 at 01:23:40PM +0100, Mark Brown wrote:
> On Wed, Jun 17, 2015 at 08:24:48AM +0530, Vinod Koul wrote:
> > > if (cpu_dai->driver->create)
> > > ret = cpu_dai->driver->create(rtd, num);
>
>
> > > and each driver passes soc_new_compress (or whatever) there. This is
> > > flexible and can be extended if any new stuff has to be handled.
> > > Even PCM creation or dai widget links can be passed in that form,
> > > too.
>
> > and the default would be snd_pcm_new so that *most* drivers dont need to add
> > this. Only Intel atom driver should add soc_new_compress() as create ops,
> > hence direct reference so no gaurds required
>
> > Looks good to me then, Mark you okay with this approach?
>
> I'm not sure this fully helps. This will put the reference in the CPU
> driver which if there's sharing with non-compressed DAIs means that any
> machine driver using the platform needs to select the compressed audio
> code. It also means that we're still in the situation whre if a machine
> *can* support compressed audio it *must* support compressed audio, it's
> not clear to me that people doing this sort of memory optimisation are
> always going to be doing it on hardware that doesn't have the capacity
> for compressed audio (or won't in the future). But then I don't know
> exactly how much memory is being saved here...
Yes this is a good point but then driver can define the compressed dai only
when SND_SOC_COMPRESS is enabled. So if machine has enabled this symbol then
only dai get added and machine can create dai-link
Also for the size question, in sound-next we have 248KB soc-compress.o
Thanks
--
~Vinod
next prev parent reply other threads:[~2015-06-17 16:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 3:20 [PATCH v2 1/2] ASoC: soc-compress: add a config item for soc-compress Jie Yang
2015-06-15 3:20 ` [PATCH v2 2/2] ASoC: soc-compress: split soc-compress to a module Jie Yang
2015-06-15 15:07 ` Mark Brown
2015-06-15 11:33 ` [PATCH v2 1/2] ASoC: soc-compress: add a config item for soc-compress Takashi Iwai
2015-06-15 14:15 ` Jie, Yang
2015-06-15 14:26 ` Takashi Iwai
2015-06-15 14:46 ` Jie, Yang
2015-06-15 15:05 ` Mark Brown
2015-06-16 0:49 ` Jie, Yang
2015-06-16 10:54 ` Mark Brown
2015-06-16 12:36 ` Jie, Yang
2015-06-16 16:06 ` Mark Brown
2015-06-16 16:14 ` Takashi Iwai
2015-06-16 16:17 ` Takashi Iwai
2015-06-16 16:25 ` Vinod Koul
2015-06-16 16:36 ` Takashi Iwai
2015-06-17 2:54 ` Vinod Koul
2015-06-17 12:23 ` Mark Brown
2015-06-17 16:22 ` Vinod Koul [this message]
2015-06-17 16:38 ` Mark Brown
2015-06-18 2:59 ` Jie, Yang
2015-06-17 11:10 ` Jie, Yang
2015-09-15 6:53 ` Jie, Yang
2015-06-16 16:29 ` Qais Yousef
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=20150617162256.GE28601@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@intel.com \
--cc=ramesh.babu@intel.com \
--cc=tiwai@suse.de \
--cc=vivian.zhang@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