From: Akhil R <akhilrajeev@nvidia.com>
To: unlisted-recipients:; (no To-header on input)
Cc: <dan.j.williams@intel.com>, <devicetree@vger.kernel.org>,
<dmaengine@vger.kernel.org>, <jonathanh@nvidia.com>,
<kyarlagadda@nvidia.com>, <ldewangan@nvidia.com>,
<linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<p.zabel@pengutronix.de>, <rgumasta@nvidia.com>,
<robh+dt@kernel.org>, <thierry.reding@gmail.com>,
<vkoul@kernel.org>, Akhil R <akhilrajeev@nvidia.com>
Subject: [PATCH v11 0/4] Add NVIDIA Tegra GPC-DMA driver
Date: Thu, 28 Oct 2021 18:53:35 +0530 [thread overview]
Message-ID: <1635427419-22478-1-git-send-email-akhilrajeev@nvidia.com> (raw)
Add support for NVIDIA Tegra general purpose DMA driver for
Tegra186 and Tegra194 platform.
Changes in patch v11:
* Removed unused label. Added description in doc
* Fixed dt_binding_check warnings.
v10 - https://lkml.org/lkml/2021/10/25/854
Akhil R (4):
dt-bindings: dmaengine: Add doc for tegra gpcdma
dmaengine: tegra: Add tegra gpcdma driver
arm64: defconfig: tegra: Enable GPCDMA
arm64: tegra: Add GPCDMA node for tegra186 and tegra194
.../bindings/dma/nvidia,tegra186-gpc-dma.yaml | 115 ++
arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi | 4 +
arch/arm64/boot/dts/nvidia/tegra186.dtsi | 44 +
arch/arm64/boot/dts/nvidia/tegra194-p2888.dtsi | 4 +
arch/arm64/boot/dts/nvidia/tegra194.dtsi | 44 +
arch/arm64/configs/defconfig | 1 +
drivers/dma/Kconfig | 12 +
drivers/dma/Makefile | 1 +
drivers/dma/tegra186-gpc-dma.c | 1279 ++++++++++++++++++++
9 files changed, 1504 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml
create mode 100644 drivers/dma/tegra186-gpc-dma.c
--
2.7.4
next reply other threads:[~2021-10-28 13:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 13:23 Akhil R [this message]
2021-10-28 13:23 ` [PATCH v11 1/4] dt-bindings: dmaengine: Add doc for tegra gpcdma Akhil R
2021-11-02 13:20 ` Rob Herring
2021-11-03 10:34 ` Akhil R
2021-11-18 23:35 ` Rob Herring
2021-10-28 13:23 ` [PATCH v11 2/4] dmaengine: tegra: Add tegra gpcdma driver Akhil R
2021-10-29 2:00 ` kernel test robot
2021-10-29 14:27 ` kernel test robot
2021-10-28 13:23 ` [PATCH v11 3/4] arm64: defconfig: tegra: Enable GPCDMA Akhil R
2021-10-28 13:23 ` [PATCH v11 4/4] arm64: tegra: Add GPCDMA node for tegra186 and tegra194 Akhil R
2021-11-09 14:35 ` [PATCH v12 0/4] Add NVIDIA Tegra GPC-DMA driver Akhil R
2021-11-09 14:35 ` [PATCH v12 1/4] dt-bindings: dmaengine: Add doc for tegra gpcdma Akhil R
2021-11-09 14:35 ` [PATCH v12 2/4] dmaengine: tegra: Add tegra gpcdma driver Akhil R
2021-11-12 19:10 ` kernel test robot
2021-11-17 17:39 ` kernel test robot
2021-11-09 14:35 ` [PATCH v12 3/4] arm64: defconfig: tegra: Enable GPCDMA Akhil R
2021-11-09 14:35 ` [PATCH v12 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=1635427419-22478-1-git-send-email-akhilrajeev@nvidia.com \
--to=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).