From: Mark Brown <broonie@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
Stephen Warren <swarren@nvidia.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Michael Wei Hong Sit <michael.wei.hong.sit@intel.com>
Subject: Re: [PATCH] ASoC: dmaengine: Document support for TX only or RX only streams
Date: Mon, 12 Oct 2020 14:37:45 +0100 [thread overview]
Message-ID: <20201012133745.GD4332@sirena.org.uk> (raw)
In-Reply-To: <20201009103124.GT4077@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 724 bytes --]
On Fri, Oct 09, 2020 at 01:31:24PM +0300, Andy Shevchenko wrote:
> What is the best way for individual ASoC drivers to be sure that at load time
> they have or have not DMA resources available?
> Now, seems the approach is to check dma-names property present and thus, try to
> switch to DMA mode, otherwise PIO. But this seems to me a bit fragile. Why ASoC
> core can't simple recognize DMA resources as optional (for the drivers that
> want to know if they available or not)?
I'm not sure what you mean by "recognize DMA resources as optional"
here? At present drivers that think something might not have appeared
should go through the resources and check them individually, anything
that hard errored won't be there.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-10-12 13:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 16:11 [PATCH] ASoC: dmaengine: Document support for TX only or RX only streams Mark Brown
2020-10-09 10:27 ` Andy Shevchenko
2020-10-09 10:31 ` Andy Shevchenko
2020-10-12 13:37 ` Mark Brown [this message]
2020-10-12 13:55 ` Andy Shevchenko
2020-10-12 15:48 ` Mark Brown
2020-10-12 16:31 ` Andy Shevchenko
2020-10-12 18:26 ` Mark Brown
2020-10-13 13:02 ` Andy Shevchenko
2020-10-09 15:01 ` 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=20201012133745.GD4332@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@intel.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=michael.wei.hong.sit@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=swarren@nvidia.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).