From: Rob Herring <robh@kernel.org>
To: Akhil R <akhilrajeev@nvidia.com>
Cc: rgumasta@nvidia.com, robh+dt@kernel.org, ldewangan@nvidia.com,
thierry.reding@gmail.com, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, jonathanh@nvidia.com,
p.zabel@pengutronix.de, kyarlagadda@nvidia.com,
dan.j.williams@intel.com, vkoul@kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v14 1/4] dt-bindings: dmaengine: Add doc for tegra gpcdma
Date: Fri, 10 Dec 2021 10:44:12 -0600 [thread overview]
Message-ID: <YbOD3F2DvkAz3tLK@robh.at.kernel.org> (raw)
In-Reply-To: <1638795639-3681-2-git-send-email-akhilrajeev@nvidia.com>
On Mon, 06 Dec 2021 18:30:36 +0530, Akhil R wrote:
> Add DT binding document for Nvidia Tegra GPCDMA controller.
>
> Signed-off-by: Rajesh Gumasta <rgumasta@nvidia.com>
> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
> Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> .../bindings/dma/nvidia,tegra186-gpc-dma.yaml | 110 +++++++++++++++++++++
> 1 file changed, 110 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2021-12-10 16:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 13:00 [PATCH v14 0/4] Add NVIDIA Tegra GPC-DMA driver Akhil R
2021-12-06 13:00 ` [PATCH v14 1/4] dt-bindings: dmaengine: Add doc for tegra gpcdma Akhil R
2021-12-10 16:44 ` Rob Herring [this message]
2021-12-06 13:00 ` [PATCH v14 2/4] dmaengine: tegra: Add tegra gpcdma driver Akhil R
2021-12-09 17:10 ` Thierry Reding
2021-12-09 21:19 ` Dmitry Osipenko
2021-12-09 21:23 ` Dmitry Osipenko
2021-12-15 13:50 ` Akhil R
2021-12-15 14:56 ` Dmitry Osipenko
2021-12-09 21:26 ` Dmitry Osipenko
2021-12-09 21:37 ` Dmitry Osipenko
2021-12-06 13:00 ` [PATCH v14 3/4] arm64: defconfig: tegra: Enable GPCDMA Akhil R
2021-12-06 13:00 ` [PATCH v14 4/4] arm64: tegra: Add GPCDMA node for tegra186 and tegra194 Akhil R
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=YbOD3F2DvkAz3tLK@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=akhilrajeev@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kyarlagadda@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=rgumasta@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=vkoul@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).