From: Hans-Christian Egtvedt <hcegtvedt@atmel.com>
To: Haavard Skinnemoen <hskinnemoen@atmel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, kernel@avr32linux.org
Subject: Re: [PATCH 2/2] ALSA sound driver for the AT73C213 DAC using Atmel SSC driver
Date: Tue, 17 Jul 2007 10:54:19 +0200 [thread overview]
Message-ID: <1184662459.12675.8.camel@localhost.localdomain> (raw)
In-Reply-To: <20070717104859.34f76382@dhcp-255-175.norway.atmel.com>
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
On Tue, 2007-07-17 at 10:48 +0200, Haavard Skinnemoen wrote:
> On Tue, 17 Jul 2007 10:37:21 +0200
> Hans-Christian Egtvedt <hcegtvedt@atmel.com> wrote:
>
> > > > + snd_pcm_set_ops(pcm, SNDRV_PCM_STREAM_PLAYBACK, &at73c213_playback_ops);
> > > > +
> > > > + retval = snd_pcm_lib_preallocate_pages_for_all(chip->pcm,
> > > > + SNDRV_DMA_TYPE_DEV,
> > > > + snd_dma_continuous_data(GFP_KERNEL),
> > > > + 64 * 1024, 64 * 1024);
> > >
> > > For SNDRV_DMA_TYPE_DEV, pass the struct device pointer of the device
> > > to the third argument. Then the pre-allocator will allocate the
> > > memory via dma_alloc_coherent() with the givn device. If it's not
> > > appropriate, SNDRV_DMA_TYPE_CONTINUOUS type. Anyway,
> > > snd_dma_continuous_data() is only for SNDRV_DMA_TYPE_CONTINUOUS.
> >
> > Ok, applied. Using &chip->spi->dev.
>
> Not that I think it matters at the moment, but that's not entirely
> correct. The memory is used for DMA transfers to the SSC controller,
> not the SPI device, so you should pass the SSC's struct device here.
>
> In other words, I think you should use &chip->ssc->pdev->dev.
Hmm, my fault, applied.
New patch attached.
--
With kind regards,
Hans-Christian Egtvedt, siv.ing. (M.Sc.)
Applications Engineer - AVR32 System Solutions - Atmel Norway
[-- Attachment #2: 0001-ALSA-sound-driver-for-the-AT73C213-DAC-using-Atmel-S.patch --]
[-- Type: application/mbox, Size: 36349 bytes --]
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2007-07-17 8:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 14:14 [PATCH 1/2] Add SPI devices to ALSA Kconfig and Makefile Hans-Christian Egtvedt
2007-07-16 14:14 ` [PATCH 2/2] ALSA sound driver for the AT73C213 DAC using Atmel SSC driver Hans-Christian Egtvedt
2007-07-16 14:15 ` Takashi Iwai
2007-07-16 14:25 ` Hans-Christian Egtvedt
2007-07-16 14:30 ` Takashi Iwai
2007-07-16 14:39 ` Takashi Iwai
2007-07-16 14:46 ` Hans-Christian Egtvedt
2007-07-16 14:47 ` Takashi Iwai
2007-07-16 14:43 ` Hans-Christian Egtvedt
2007-07-16 14:48 ` Takashi Iwai
2007-07-16 15:08 ` Takashi Iwai
2007-07-16 15:27 ` Haavard Skinnemoen
2007-07-16 15:32 ` Takashi Iwai
2007-07-17 8:37 ` Hans-Christian Egtvedt
2007-07-17 8:48 ` Haavard Skinnemoen
2007-07-17 8:54 ` Hans-Christian Egtvedt [this message]
2007-07-17 10:23 ` Takashi Iwai
2007-07-17 11:23 ` Hans-Christian Egtvedt
2007-07-17 11:36 ` Haavard Skinnemoen
2007-07-23 14:49 ` Takashi Iwai
2007-07-26 6:21 ` Hans-Christian Egtvedt
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=1184662459.12675.8.camel@localhost.localdomain \
--to=hcegtvedt@atmel.com \
--cc=alsa-devel@alsa-project.org \
--cc=hskinnemoen@atmel.com \
--cc=kernel@avr32linux.org \
--cc=tiwai@suse.de \
/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