All of lore.kernel.org
 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 2/2] davinci: da850evm: enable mcasp ping-pong bufs and evq's
Date: Thu, 19 May 2011 14:14:06 -0700	[thread overview]
Message-ID: <20110519211406.GE18849@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <f02f2bda26f87fff2bb9e958baa12672cae7e362.1305723716.git.bengardiner@nanometrics.ca>

On Wed, May 18, 2011 at 09:27:46AM -0400, Ben Gardiner wrote:
> The davinci-mcasp driver will copy the platform data specified sram sizes and
> eventq's.
> 
> Set the event queues and sram sizes for da850. 8K SRAM buffers are selected
> because it is the minimum that resulted in the same period size when testing
> 48KHz S16_LE stereo. Event queues 0 and 1 are assigned to match those 
> specified by Troy Kisky in his introduction of ping-pong buffers for dm644x.
> 
> Signed-off-by: Ben Gardiner <bengardiner@nanometrics.ca>

Davinci folks, are you OK with this?

  reply	other threads:[~2011-05-19 21:14 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
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 [this message]
     [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=20110519211406.GE18849@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 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.