alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@nokia.com>
To: alsa-devel@alsa-project.org
Cc: "tony@atomide.com" <tony@atomide.com>,
	"broonie@opensource.wolfsonmicro.com"
	<broonie@opensource.wolfsonmicro.com>,
	"Valentin Eduardo (Nokia-D/Helsinki)"
	<eduardo.valentin@nokia.com>,
	"Nurkkala Eero.An (EXT-Offcode/Oulu)"
	<ext-Eero.Nurkkala@nokia.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	ext Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [RFC PATCH 5/5] ASoC: omap-mcbsp: Place correct constraints for streams
Date: Mon, 31 May 2010 14:57:22 +0300	[thread overview]
Message-ID: <201005311457.22699.peter.ujfalusi@nokia.com> (raw)
In-Reply-To: <1275300021.3174.5.camel@odin>

On Monday 31 May 2010 13:00:21 ext Liam Girdwood wrote:

...

> > +static int hw_rule_bsize_by_channels(struct snd_pcm_hw_params *params,
> > +				    struct snd_pcm_hw_rule *rule)
> > +{
> > +	struct snd_interval *bs = hw_param_interval(params,
> > +					SNDRV_PCM_HW_PARAM_BUFFER_SIZE);
> > +	struct snd_interval *c = hw_param_interval(params,
> > +					SNDRV_PCM_HW_PARAM_CHANNELS);
> 
> Best to make these variable names more meaningful.

Sure, I can change that. I have picked these, since all code, which adds hw_rule 
(and the writing an ALSA driver manual) are using variables like this.
In Here I mean:
bs == Buffer Size
c == Channels

> 
> > +	struct omap_mcbsp_data *mcbsp_data = rule->private;
> > +	struct snd_interval frames;
> > +	int size;
> > +
> > +	snd_interval_any(&frames);
> > +	size = omap_mcbsp_get_fifo_size(mcbsp_data->bus_id);
> > +
> > +	frames.min = size / c->min;
> > +	frames.integer = 1;
> > +	return snd_interval_refine(bs, &frames);
> > +
> > +}
> > +
> > +static int hw_rule_psize_by_channels(struct snd_pcm_hw_params *params,
> > +				    struct snd_pcm_hw_rule *rule)
> > +{
> > +	struct snd_interval *ps = hw_param_interval(params,
> > +					SNDRV_PCM_HW_PARAM_PERIOD_SIZE);
> > +	struct snd_interval *c = hw_param_interval(params,
> > +					SNDRV_PCM_HW_PARAM_CHANNELS);
> 
> ditto

Same here:
I mean:
ps == Period Size
c == Channels

> 
> Thanks
> 
> Liam

Never the less, I can change them, 

Thanks,
Péter

  reply	other threads:[~2010-05-31 11:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31  8:16 [RFC PATCH 0/5] OMAP/ASoC: McBSP: FIFO handling related fixes Peter Ujfalusi
2010-05-31  8:16 ` [RFC PATCH 1/5] OMAP: McBSP: Function to query the FIFO size Peter Ujfalusi
2010-05-31  8:16 ` [RFC PATCH 2/5] OMAP3: McBSP: Change the way how the FIFO is handled Peter Ujfalusi
2010-05-31 17:41   ` Nishanth Menon
2010-06-01  6:59     ` Peter Ujfalusi
2010-06-02  4:24       ` Nishanth Menon
2010-05-31  8:16 ` [RFC PATCH 3/5] OMAP3: McBSP: Use the port's buffer_size when calculating tx delay Peter Ujfalusi
2010-05-31  8:16 ` [RFC PATCH 4/5] ASoC: omap-mcbsp: Save, and use wlen for threshold configuration Peter Ujfalusi
2010-05-31  8:16 ` [RFC PATCH 5/5] ASoC: omap-mcbsp: Place correct constraints for streams Peter Ujfalusi
2010-05-31  8:41   ` Peter Ujfalusi
2010-05-31 10:00   ` [alsa-devel] " Liam Girdwood
2010-05-31 11:57     ` Peter Ujfalusi [this message]
2010-06-01  6:38       ` Jarkko Nikula
2010-06-01  6:47         ` Peter Ujfalusi
2010-06-01  7:38           ` Jarkko Nikula
2010-06-01  8:07             ` Peter Ujfalusi
2010-06-01  8:19             ` Peter Ujfalusi
2010-06-01  9:29               ` Jarkko Nikula
2010-06-01 10:30                 ` Peter Ujfalusi
2010-06-01 11:20                   ` [alsa-devel] " Jarkko Nikula
2010-06-01 11:34                     ` Peter Ujfalusi
  -- strict thread matches above, loose matches on Subject: below --
2010-05-31  8:03 [RFC PATCH 0/5] OMAP/ASoC: McBSP: FIFO handling related fixes Peter Ujfalusi
2010-05-31  8:03 ` [RFC PATCH 5/5] ASoC: omap-mcbsp: Place correct constraints for streams Peter Ujfalusi
2010-05-31  8:09   ` Peter Ujfalusi

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=201005311457.22699.peter.ujfalusi@nokia.com \
    --to=peter.ujfalusi@nokia.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=eduardo.valentin@nokia.com \
    --cc=ext-Eero.Nurkkala@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=lrg@slimlogic.co.uk \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).