All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@sig21.net>
To: Steve Calfee <stevecalfee@gmail.com>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Ashish Chavan <ashish.chavan@kpitcummins.com>
Subject: Re: Template Based Coefficients Setting for Filters
Date: Tue, 9 Aug 2011 23:28:24 +0200	[thread overview]
Message-ID: <20110809212824.GA4241@sig21.net> (raw)
In-Reply-To: <4E416C1F.6030301@gmail.com>

(add back Cc:s)

Hi Steve,

On Tue, Aug 09, 2011 at 10:19:27AM -0700, Steve Calfee wrote:
> On 08/09/11 08:16, Mark Brown wrote:
> > On Tue, Aug 09, 2011 at 06:03:56PM +0530, Ashish Chavan wrote:
> > 
> >>    I am working on updating ASoC codec driver for Dialog's DA7210 codec
> >> (sound/soc/codec/da7210.c). This update would be a major functionality
> >> update in nature. Currently, I am implementing support for GP (general
> >> purpose) filters of this codec and need some opinions/comments.
> > 
> > Use _BYTES controls for this.  There are no existing users in ASoC,
> > though there should be shortly and there are generic ALSA examples.
> 
> Hi Mark,
> 
> Could you expand on this. Neither google or lxr found anything about
> _BYTES controls. Where is it defined in the source?

I've written a driver for ST32x, it will be in 3.1.  My patch
to use _BYTES controls were posted here not long ago, see
http://thread.gmane.org/gmane.linux.alsa.devel/87063


HTH
Johannes

  reply	other threads:[~2011-08-09 21:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09 12:33 Template Based Coefficients Setting for Filters Ashish Chavan
2011-08-09 15:16 ` Mark Brown
2011-08-09 17:19   ` Steve Calfee
2011-08-09 21:28     ` Johannes Stezenbach [this message]
2011-08-09 23:33       ` Mark Brown
2011-08-10  6:17         ` Takashi Iwai
2011-08-12  8:19       ` Ashish Chavan

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=20110809212824.GA4241@sig21.net \
    --to=js@sig21.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=ashish.chavan@kpitcummins.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=stevecalfee@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.