From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
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: Mon, 15 Jul 2013 22:27:21 +0530 [thread overview]
Message-ID: <20130715165721.GV16653@intel.com> (raw)
In-Reply-To: <20130715172643.GZ11538@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
On Mon, Jul 15, 2013 at 06:26:43PM +0100, Mark Brown wrote:
> On Mon, Jul 15, 2013 at 06:42:10PM +0200, Lars-Peter Clausen wrote:
>
> > + hw.period_bytes_min = 16;
> > + hw.period_bytes_max = dma_caps.max_sg_len;
>
> We can't read the minimum period size from dmaengine? Seems like
> something might have a restriction other than 16 bytes here.
max would be how many list items the engine supports so queried therotical min
would be 1 byte, not sure how 16 bytes is assumed above but my guess is that if
engine is able to push min burst lengths which would be 1 and give you
interrupt. But seriously, that would not be practical. So this should be a
realistic limit which system can cope with.
~Vinod
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-07-15 16:57 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 [this message]
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
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=20130715165721.GV16653@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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).