All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Jean-Francois Moine <moinejf@free.fr>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
	Rob Herring <rob.herring@calxeda.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 4/4] ASoc: kirkwood: add DT support
Date: Fri, 26 Jul 2013 12:05:54 +0100	[thread overview]
Message-ID: <20130726110554.GB9858@sirena.org.uk> (raw)
In-Reply-To: <20130725230533.GH24642@n2100.arm.linux.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]

On Fri, Jul 26, 2013 at 12:05:33AM +0100, Russell King - ARM Linux wrote:
> On Thu, Jul 25, 2013 at 08:19:05PM +0100, Mark Brown wrote:
> > On Thu, Jul 25, 2013 at 11:14:59AM +0200, Jean-Francois Moine wrote:

> > > +	if (np) {
> > > +		priv->burst = 128;		/* might be 32 or 128 */
> > > +	} else if (data) {

> > When you posted this before I queried how and why the value might vary -
> > I see the code is the same and I don't recall a reply.

> This is the DMA burst size, and can be either 32 or 128 bytes according
> to the docs.  Everyone seems to pass this as 128 bytes in their platform
> data to date, which I guess is why its ended up being hard coded as 128.

OK.

> However, whether it needs to be configurable or not is debatable - obviously
> the hardware allows it, but that doesn't mean it has to be exposed.  If
> ALSA has some kind of way of specifying a "low latency" mode where 128
> byte vs 32 byte fetches would make a significant difference, then it may
> be something to look at.

This sort of configuration would normally be keyed off the period size
and so vary at runtime depending on what the application does when it
opens a stream.  Sounds like something someone can worry about if they
have the requirement.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2013-07-26 11:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25  9:14 [PATCH 4/4] ASoc: kirkwood: add DT support Jean-Francois Moine
2013-07-25 19:19 ` Mark Brown
2013-07-25 19:19   ` Mark Brown
2013-07-25 23:05   ` Russell King - ARM Linux
2013-07-25 23:05     ` Russell King - ARM Linux
2013-07-26  9:09     ` Jean-Francois Moine
2013-07-26  9:21       ` Russell King - ARM Linux
2013-07-26  9:21         ` Russell King - ARM Linux
2013-07-26  9:49         ` Jean-Francois Moine
2013-07-26 11:05     ` Mark Brown [this message]

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=20130726110554.GB9858@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=moinejf@free.fr \
    --cc=perex@perex.cz \
    --cc=rob.herring@calxeda.com \
    --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 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.