public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Vinod Koul <vinod.koul@intel.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC 1/2] ASoC: dmaengine-pcm: Add support for querying DMA capabilities
Date: Tue, 16 Jul 2013 11:03:57 +0100	[thread overview]
Message-ID: <20130716100357.GE22506@sirena.org.uk> (raw)
In-Reply-To: <51E50D3B.2050207@metafoo.de>

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

On Tue, Jul 16, 2013 at 11:07:07AM +0200, Lars-Peter Clausen wrote:

> I would assume that most of them don't express hardware limitations but
> rather are sensible lower limits which allow operation without
> over-/underruns. But that's something that doesn't necessarily depend on the

Yes, indeed.  Or just cut'n'pasted from some other driver without much
thought.

> DMA controller, but rather on the system as a whole, e.g. on a slower
> machine you'd typically set the limit higher so the CPU has a better chance
> to keep up. So this isn't something you'd want to set in the DMA controller
> driver. But I'm not sure if there is a good way to calculate a sensible
> minimum buffer size based on the whole system's constraints.

Not really.  It's going to depend on userspace as well, and things like
SMIs on systems with those.

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

      reply	other threads:[~2013-07-16 10:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 16:42 [RFC 1/2] ASoC: dmaengine-pcm: Add support for querying DMA capabilities Lars-Peter Clausen
2013-07-15 16:42 ` [RFC 2/2] ASoC: dmaengine-pcm: Provide default config Lars-Peter Clausen
2013-07-15 17:26 ` [RFC 1/2] ASoC: dmaengine-pcm: Add support for querying DMA capabilities Mark Brown
2013-07-15 16:57   ` Vinod Koul
2013-07-15 17:57     ` Mark Brown
2013-07-15 18:20       ` Lars-Peter Clausen
2013-07-15 19:51         ` Mark Brown
2013-07-16  9:07           ` Lars-Peter Clausen
2013-07-16 10:03             ` 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=20130716100357.GE22506@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vinod.koul@intel.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