All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Timur Tabi <timur@freescale.com>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Is params_format() valid in the _hw_params() function?
Date: Wed, 16 Jul 2008 10:40:50 +0200	[thread overview]
Message-ID: <487DB412.2090105@ladisch.de> (raw)
In-Reply-To: <487D1FCA.9030605@freescale.com>

Timur Tabi wrote:
> My ASoC driver programs the sample size in the _prepare() callback function,
> because I was under the impression that the sample size cannot be known in the
> _hw_params() callback function.  However, I just ran a test, and it appears that
> the params_format() macro does return the right value.  Once I know the format,
> I can determine the same size.
>
> Is this always true, even in OSS emulation?

Yes.  The OSS emulation pretends to be an ALSA application.

> I know very little about ALSA and OSS application programming, so I
> don't know what causes _hw_params() to be called vs. _prepare().

*_hw_params() is called to set sample format/rate and buffer parameters.
In most cases, it is called once when the device is initialized, but it
can be called multiple times if an application wants to change some of
these parameters.  (The latter happens with OSS emulation because the
various OSS ioctl calls change only one of multiple parameters.)

*_prepare() is called before a device is started.  It can be called
multiple times without intervening _hw_params() calls when the device
is started/stopped multiple times.


HTH
Clemens

      reply	other threads:[~2008-07-16  8:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 22:08 Is params_format() valid in the _hw_params() function? Timur Tabi
2008-07-16  8:40 ` Clemens Ladisch [this message]

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=487DB412.2090105@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=timur@freescale.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.