From: Timur Tabi <timur@freescale.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Trent Piepho <xyzzy@speakeasy.org>
Subject: Re: hw_params function and OSS emulation
Date: Wed, 22 Aug 2007 16:08:49 -0500 [thread overview]
Message-ID: <46CCA5E1.5050704@freescale.com> (raw)
In-Reply-To: <s5h7innnuv3.wl%tiwai@suse.de>
Takashi Iwai wrote:
> The buffer allocation in prepare callback would actually do work.
> I've never mentioned that it doesn't work. It's just not
> recommended, simply because the prepare is called more often than
> hw_params even without changing the parameters.
What is the driver supposed to do on the second call to .prepare()? In other
words, what is the point of calling it multiple times in a row? Once my
driver is prepared to start, how could it become more prepared?
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-08-22 21:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 18:15 hw_params function and OSS emulation Timur Tabi
2007-08-21 23:42 ` Trent Piepho
2007-08-22 9:17 ` Takashi Iwai
2007-08-22 14:28 ` Timur Tabi
2007-08-22 14:59 ` Takashi Iwai
2007-08-22 15:02 ` Timur Tabi
2007-08-22 15:39 ` Takashi Iwai
2007-08-22 15:48 ` Timur Tabi
2007-08-22 15:57 ` Takashi Iwai
2007-08-23 17:36 ` Timur Tabi
2007-08-23 17:40 ` Takashi Iwai
2007-08-23 18:43 ` Timur Tabi
2007-08-23 19:01 ` Takashi Iwai
2007-08-23 19:13 ` Timur Tabi
2007-08-23 19:35 ` Takashi Iwai
2007-08-23 22:17 ` Trent Piepho
2007-08-22 20:25 ` Trent Piepho
2007-08-22 21:05 ` Takashi Iwai
2007-08-22 21:08 ` Timur Tabi [this message]
2007-08-22 21:57 ` Takashi Iwai
2007-08-22 22:08 ` Timur Tabi
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=46CCA5E1.5050704@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
--cc=xyzzy@speakeasy.org \
/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.