From: Stephen Warren <swarren@wwwdotorg.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
Vinod Koul <vinod.koul@intel.com>,
Thierry Reding <thierry.reding@gmail.com>,
Alexandre Courbot <gnurou@gmail.com>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>, Arnd Bergmann <arnd@arndb.de>,
dmaengine@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/2] Documentation: DT: Add binding documentation for NVIDIA ADMA
Date: Tue, 6 Oct 2015 17:04:09 -0600 [thread overview]
Message-ID: <56145369.7040404@wwwdotorg.org> (raw)
In-Reply-To: <1444047007-30494-2-git-send-email-jonathanh@nvidia.com>
On 10/05/2015 06:10 AM, Jon Hunter wrote:
> Add device-tree binding documentation for the Tegra210 Audio DMA
> controller.
> diff --git a/Documentation/devicetree/bindings/dma/tegra210-adma.txt b/Documentation/devicetree/bindings/dma/tegra210-adma.txt
> +- #dma-cells : Must be <2>. The first cell denotes the transmit or
> + receive request number and should be between 1 and the maximum number
> + of requests supported (see properties "dma-rx-requests" and
> + "dma-tx-requests"). This value corresponds to the RX/TX_REQUEST_SELECT
> + fields in the ADMA_CHn_CTRL register. The second cell denotes whether
> + the channel is a receive or transmit channel and must be either 2 for
> + a receive channel and 4 for a transmit channel. These values correspond
> + to the TRANSFER_DIRECTION field of the ADMA_CHn_CTRL register.
Is it typical to encode the direction into the dma cells? I would have
thought the client would provide that information at run-time when
requesting a DMA channel.
next prev parent reply other threads:[~2015-10-06 23:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 12:10 [PATCH V2 0/2] Add support for Tegra210 ADMA Jon Hunter
2015-10-05 12:10 ` [PATCH V2 1/2] Documentation: DT: Add binding documentation for NVIDIA ADMA Jon Hunter
2015-10-05 13:12 ` Mark Rutland
2015-10-06 9:16 ` Jon Hunter
2015-10-06 22:57 ` Stephen Warren
2015-10-07 15:26 ` Jon Hunter
2015-10-07 16:05 ` Stephen Warren
2015-10-07 16:33 ` Mark Rutland
2015-10-06 23:04 ` Stephen Warren [this message]
2015-10-07 8:43 ` Jon Hunter
2015-10-07 16:09 ` Stephen Warren
2015-10-07 16:19 ` Jon Hunter
2015-10-07 19:36 ` Stephen Warren
2015-10-08 9:58 ` Jon Hunter
2015-10-08 14:27 ` Stephen Warren
2015-10-09 10:20 ` Jon Hunter
2015-10-09 15:26 ` Stephen Warren
2015-10-12 13:55 ` Jon Hunter
2015-10-12 17:51 ` Stephen Warren
2015-10-13 12:56 ` Jon Hunter
2015-10-07 16:38 ` Mark Rutland
2015-10-05 12:10 ` [PATCH V2 2/2] dmaengine: tegra-adma: Add support for Tegra210 ADMA Jon Hunter
2015-10-06 9:32 ` Arnd Bergmann
2015-10-06 9:45 ` Jon Hunter
2015-10-14 11:27 ` Vinod Koul
2015-10-14 13:34 ` Jon Hunter
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=56145369.7040404@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=arnd@arndb.de \
--cc=dmaengine@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).