From: Akhil R <akhilrajeev@nvidia.com>
To: <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>
Cc: <akhilrajeev@nvidia.com>
Subject: [PATCH v20 0/2] Add NVIDIA Tegra GPC-DMA driver
Date: Mon, 21 Feb 2022 21:09:32 +0530 [thread overview]
Message-ID: <20220221153934.5226-1-akhilrajeev@nvidia.com> (raw)
Add support for NVIDIA Tegra general purpose DMA driver for
Tegra186 and Tegra194 platform.
v19->v20:
* Change in sg_idx updation to solve issue when sg_idx=0 in cyclic
transfers
* Styling and spacing changes
Akhil R (2):
dt-bindings: dmaengine: Add doc for tegra gpcdma
dmaengine: tegra: Add tegra gpcdma driver
.../bindings/dma/nvidia,tegra186-gpc-dma.yaml | 110 ++
drivers/dma/Kconfig | 11 +
drivers/dma/Makefile | 1 +
drivers/dma/tegra186-gpc-dma.c | 1507 +++++++++++++++++
4 files changed, 1629 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra186-gpc-dma.yaml
create mode 100644 drivers/dma/tegra186-gpc-dma.c
--
2.17.1
next reply other threads:[~2022-02-21 15:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 15:39 Akhil R [this message]
2022-02-21 15:39 ` [PATCH v20 1/2] dt-bindings: dmaengine: Add doc for tegra gpcdma Akhil R
2022-02-21 15:39 ` [PATCH v20 2/2] dmaengine: tegra: Add tegra gpcdma driver Akhil R
2022-02-22 4:59 ` kernel test robot
2022-02-22 15:31 ` Nathan Chancellor
2022-02-23 3:49 ` Akhil R
2022-02-23 18:43 ` Nathan Chancellor
2022-02-24 4:23 ` Akhil R
2022-02-24 4:38 ` Vinod Koul
2022-02-22 21:38 ` kernel test robot
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=20220221153934.5226-1-akhilrajeev@nvidia.com \
--to=akhilrajeev@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.