From: Vinod Koul <vinod.koul@intel.com>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
Eric Long <eric.long@spreadtrum.com>,
Mark Brown <broonie@kernel.org>,
dmaengine@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: [4/5] dmaengine: sprd: Add Spreadtrum DMA configuration
Date: Mon, 16 Apr 2018 21:05:01 +0530 [thread overview]
Message-ID: <20180416153501.GQ6014@localhost> (raw)
On Mon, Apr 16, 2018 at 02:32:05PM +0800, Baolin Wang wrote:
> >> Beside the general configuration, our audio driver will configure the
> >> fragment length, block length, maybe transaction length, and they must
> >> specify the request type and interrupt type, these are what we want to
> >> export for users.
> >
> > As I said before, you need to derive fragment, block or transaction from
>
> I am sorry I did not make things clear here. What I mean is not only
> link list mode(prep_cyclic), but also other modes (prep_slave,
> prep_interleaved ...), users still need to configure the fragment
> length, block length or transaction length according to their
> requirements.
Other modes are similar, they also use the parameters programmed from
dma_slave_config. Pls see other driver examples. IIRC dw dma has
similar capabilities but not all are exposed to user and driver configures.
next reply other threads:[~2018-04-16 15:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 15:35 Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-17 6:06 [4/5] dmaengine: sprd: Add Spreadtrum DMA configuration Baolin Wang
2018-04-16 6:32 Baolin Wang
2018-04-16 3:58 Vinod Koul
2018-04-13 10:48 Baolin Wang
2018-04-13 10:11 Vinod Koul
2018-04-13 6:41 Baolin Wang
2018-04-13 6:36 Vinod Koul
2018-04-13 6:17 Baolin Wang
2018-04-13 5:44 Baolin Wang
2018-04-13 3:43 Vinod Koul
2018-04-13 3:39 Vinod Koul
2018-04-12 11:36 Baolin Wang
2018-04-12 11:30 Baolin Wang
2018-04-12 9:37 Vinod Koul
2018-04-11 12:13 Baolin Wang
2018-04-11 9:36 Vinod Koul
2018-04-10 7:46 Baolin Wang
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=20180416153501.GQ6014@localhost \
--to=vinod.koul@intel.com \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=eric.long@spreadtrum.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