alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ben Gardiner <bengardiner@nanometrics.ca>
Cc: davinci-linux-open-source@linux.davincidsp.com,
	Subhasish Ghosh <subhasish@mistralsolutions.com>,
	Sekhar Nori <nsekhar@ti.com>,
	alsa-devel@alsa-project.org,
	Troy Kisky <troy.kisky@boundarydevices.com>,
	Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 1/2] ASoC: davinci-mcasp: enable ping-pong SRAM buffers
Date: Thu, 19 May 2011 14:13:45 -0700	[thread overview]
Message-ID: <20110519211344.GD18849@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <f28f86fbe10a8cafeb04b4066b781efb7b3913b8.1305723716.git.bengardiner@nanometrics.ca>

On Wed, May 18, 2011 at 09:27:45AM -0400, Ben Gardiner wrote:
> The davinci-i2s driver copies the platform data for playback and capture
> sram sizes which is in turn used by davinci-pcm to allocate ping-pong
> buffers.
> 
> Copy also the platform data in davinci-mcasp probe.
> 
> Signed-off-by: Ben Gardiner <bengardiner@nanometrics.ca>

Applied, thanks.

  reply	other threads:[~2011-05-19 21:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-18 13:27 [PATCH 0/2] ASoC: davinci: ping-pong buffers for mcasp on da850evm Ben Gardiner
2011-05-18 13:27 ` [PATCH 1/2] ASoC: davinci-mcasp: enable ping-pong SRAM buffers Ben Gardiner
2011-05-19 21:13   ` Mark Brown [this message]
2011-05-18 13:27 ` [PATCH 2/2] davinci: da850evm: enable mcasp ping-pong bufs and evq's Ben Gardiner
2011-05-19 21:14   ` Mark Brown
     [not found]     ` <20110519211406.GE18849-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2011-05-20  7:08       ` Nori, Sekhar
2011-05-20  9:05         ` Liam Girdwood
2011-05-19 11:08 ` [PATCH 0/2] ASoC: davinci: ping-pong buffers for mcasp on da850evm Liam Girdwood

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=20110519211344.GD18849@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bengardiner@nanometrics.ca \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=lrg@ti.com \
    --cc=nsekhar@ti.com \
    --cc=subhasish@mistralsolutions.com \
    --cc=troy.kisky@boundarydevices.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).