All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
	Peter Ujfalusi <peter.ujfalusi@nokia.com>,
	Graeme Gregory <gg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC - Add support for upto 16 channels on OMAP MCBSP
Date: Fri, 06 Nov 2009 14:25:20 +0000	[thread overview]
Message-ID: <1257517520.3624.564.camel@odin> (raw)
In-Reply-To: <20091106132024.GA4938@sirena.org.uk>

On Fri, 2009-11-06 at 13:20 +0000, Mark Brown wrote:
> On Thu, Nov 05, 2009 at 08:08:30PM +0000, Liam Girdwood wrote:
> > On Thu, 2009-11-05 at 21:28 +0200, Jarkko Nikula wrote:
> 
> > > Would be nice if both the divider and frame size are calculated
> > > dynamically based on CLKSRG frequency and sample rate.
> 
> > This does sound like a useful feature and should probably exist in
> > soc-core for other platforms too.
> 
> A lot of drivers would probably have trouble using this due to the
> number of different constraints in the dividers that can be set up that
> random hardware has - it'd probably take more effort to finesse things
> than it's worth - but a utility function for mostly unconstrained
> hardware would be good.

I was thinking more generic here. e.g. additions to soc.h :-

static inline int snd_soc_get_framesize(int clock, struct snd_pcm_hw_params *params);

A caller could vary clock based upon it's divider options. Error would
be returned if there was not enough bandwidth.

and

static inline int snd_soc_get_divider(int clock, struct snd_pcm_hw_params *params);

This would return the integer divider required or bandwidth error.

and

static inline int snd_soc_get_min_clock(struct snd_pcm_hw_params *params);

return min bit clock required for params.

Liam

  reply	other threads:[~2009-11-06 14:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 17:53 [PATCH] ASoC - Add support for upto 16 channels on OMAP MCBSP Liam Girdwood
2009-11-04 18:28 ` Mark Brown
2009-11-04 18:55 ` Graeme Gregory
2009-11-04 19:46   ` Liam Girdwood
2009-11-05  7:51     ` Jarkko Nikula
2009-11-05 14:55       ` Liam Girdwood
2009-11-05 19:28         ` Jarkko Nikula
2009-11-05 20:08           ` Liam Girdwood
2009-11-06 13:20             ` Mark Brown
2009-11-06 14:25               ` Liam Girdwood [this message]
2009-11-06 15:00                 ` Mark Brown
2009-11-05  8:14   ` Peter Ujfalusi
2009-11-05  8:26 ` Peter Ujfalusi
2009-11-05 10:05   ` 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=1257517520.3624.564.camel@odin \
    --to=lrg@slimlogic.co.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=gg@slimlogic.co.uk \
    --cc=peter.ujfalusi@nokia.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.