linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org
Subject: Re: [Alsa-devel] [RFC 4/8] snd-aoa: add i2sbus
Date: Wed, 07 Jun 2006 14:58:34 +0200	[thread overview]
Message-ID: <s5hpshl5dhh.wl%tiwai@suse.de> (raw)
In-Reply-To: <1149684747.3999.24.camel@johannes>

At Wed, 07 Jun 2006 14:52:25 +0200,
Johannes Berg wrote:
> 
> On Wed, 2006-06-07 at 14:49 +0200, Takashi Iwai wrote:
> 
> > Sorry, s/pci_to_dev/snd_dma_pci_data/
> 
> So then you're saying that indeed, snd_pcm_lib_preallocate_pages_for_all
> has the side effect of setting a pointer somewhere else?

Well, I don't understand what you mean "side-effect" here.

The device pointer is passed to the memory allocator, so if you pass a
bogus value there, it'll cause surely oops.

> I just don't understand why it all blows up when I leave off the
> preallocate call. From the function name that says 'preallocate pages'
> it seemed to me that I should be allowed to just leave it off, risking
> that later an open() or prepare() fails because no pages could be
> allocated.

IIF you use snd_pcm_lib_malloc_pages(), the pre-allocation is
mandatory.  That's the definition.
(And, as mentioned, snd_pcm_lib_malloc_pages() checks the
pre-allocation when debug option is set.  If you don't set the debug
option, it assumes that the pre-allocation was already executed.)

You're free to use dma_alloc_coherent() or whatever in hw_params
callback.


Takashi

  reply	other threads:[~2006-06-07 12:58 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01 11:58 [RFC 0/8] snd-aoa: add snd-aoa Johannes Berg
2006-06-01 11:58 ` [RFC 1/8] snd-aoa: add aoa header files Johannes Berg
2006-06-01 11:58 ` [RFC 2/8] snd-aoa: add aoa core Johannes Berg
2006-06-02 13:42   ` [Alsa-devel] " Takashi Iwai
2006-06-02 13:46     ` Johannes Berg
2006-06-01 11:58 ` [RFC 3/8] snd-aoa: add soundbus Johannes Berg
2006-06-02 13:53   ` [Alsa-devel] " Takashi Iwai
2006-06-02 14:07     ` Johannes Berg
2006-06-02 14:21       ` Takashi Iwai
2006-06-02 14:41         ` Andreas Schwab
2006-06-02 14:44           ` Johannes Berg
2006-06-02 14:45           ` Takashi Iwai
2006-06-01 11:58 ` [RFC 4/8] snd-aoa: add i2sbus Johannes Berg
2006-06-02 14:23   ` [Alsa-devel] " Takashi Iwai
2006-06-06 11:17     ` Johannes Berg
2006-06-06 14:00       ` Takashi Iwai
2006-06-07 11:40         ` Johannes Berg
2006-06-07 12:41           ` Takashi Iwai
2006-06-07 12:45             ` Johannes Berg
2006-06-07 12:49               ` Takashi Iwai
2006-06-07 12:52                 ` Johannes Berg
2006-06-07 12:58                   ` Takashi Iwai [this message]
2006-06-07 13:01                     ` Johannes Berg
2006-06-01 11:58 ` [RFC 5/8] snd-aoa: add codecs Johannes Berg
2006-06-02 14:31   ` [Alsa-devel] " Takashi Iwai
2006-06-06 11:36     ` Johannes Berg
2006-06-01 11:58 ` [RFC 6/8] snd-aoa: add layout-id fabric Johannes Berg
2006-06-01 11:58 ` [RFC 7/8] snd-aoa: add Kconfig and Makefile Johannes Berg
2006-06-01 11:58 ` [RFC 8/8] snd-aoa: wire up aoa in sound/ Johannes Berg
2006-06-02 14:43 ` [Alsa-devel] [RFC 0/8] snd-aoa: add snd-aoa Takashi Iwai
2006-06-02 14:56   ` Johannes Berg
2006-06-02 15:23     ` Takashi Iwai

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=s5hpshl5dhh.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=johannes@sipsolutions.net \
    --cc=linuxppc-dev@ozlabs.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 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).