From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: "Jie, Yang" <yang.jie@intel.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>
Subject: Re: [PATCH v4] ASoC: soc-compress: add config item for soc-compress to make it compiled only when needed
Date: Wed, 14 Oct 2015 13:46:59 +0100 [thread overview]
Message-ID: <20151014124659.GN8805@ck-lbox> (raw)
In-Reply-To: <E7B1D079BA13FB44A978CC8F69C7D6A9229C6351@SHSMSX101.ccr.corp.intel.com>
On Wed, Oct 14, 2015 at 12:57:38PM +0000, Jie, Yang wrote:
> > > int (*suspend)(struct snd_soc_dai *dai);
> > > int (*resume)(struct snd_soc_dai *dai);
> > > /* compress dai */
> > > - bool compress_dai;
> > > + int (*compress_new)(struct snd_soc_pcm_runtime *rtd, int num);
> >
> > This feels a little awkward to be using a function pointer here.
> > It somewhat implies I might want to customise this function but am I every
> > going to want to set this to something other than snd_soc_new_compress?
>
> Hi Charles, we used compress_dai bool before(in v2), but for that we need
> add empty inline soc_compress_new(), Takashi suggest we use callback
> func pointer here, it can be compress_new or any other creation here.
> This is flexible and can be extended if any new stuff has to be handled.
If everyone else is happy with it, then I don't mind. It
obviously works, just felt a little odd to me.
Thanks,
Charles
next prev parent reply other threads:[~2015-10-14 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 15:41 [PATCH v4] ASoC: soc-compress: add config item for soc-compress to make it compiled only when needed Jie Yang
2015-10-14 9:20 ` Charles Keepax
2015-10-14 12:57 ` Jie, Yang
2015-10-14 12:46 ` Charles Keepax [this message]
2015-10-19 14:22 ` Jie, Yang
2015-10-22 12:51 ` Mark Brown
2015-10-22 23:09 ` Applied "ASoC: compress: add config item for soc-compress to make it compiled only when needed" to the asoc tree 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=20151014124659.GN8805@ck-lbox \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@intel.com \
--cc=yang.jie@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