public inbox for dmaengine@vger.kernel.org
 help / color / mirror / Atom feed
From: Sanjay R Mehta <Sanju.Mehta@amd.com>
To: <vkoul@kernel.org>
Cc: <gregkh@linuxfoundation.org>, <dan.j.williams@intel.com>,
	<robh@kernel.org>, <mchehab+samsung@kernel.org>,
	<davem@davemloft.net>, <linux-kernel@vger.kernel.org>,
	<dmaengine@vger.kernel.org>, Sanjay R Mehta <sanju.mehta@amd.com>
Subject: [PATCH 0/3] Add support for AMD AE4DMA controller driver
Date: Mon, 11 Sep 2023 14:25:21 -0500	[thread overview]
Message-ID: <1694460324-60346-1-git-send-email-Sanju.Mehta@amd.com> (raw)

From: Sanjay R Mehta <sanju.mehta@amd.com>

This patch series add support for AMD AE4DMA controller which
performs high bandwidth memory-to-memory and IO copy operation,
performs DMA transfer through queue based descriptor management.

The AE4DMA controller allows for configuration of the number of
queues per controller, with a range from 1 to 16. This configuration
can be conveniently adjusted using the driver's "max_hw_q" parameter.

The AMD Processor features multiple ae4dma device instances,
with each controller supporting a maximum of 16 DMA queues.

Sanjay R Mehta (3):
  dmaengine: ae4dma: Initial ae4dma controller driver with multi channel
  dmaengine: ae4dma: register AE4DMA controller as a DMA resource
  dmaengine: ae4dma: Add debugfs entries for AE4DMA

 MAINTAINERS                           |   6 +
 drivers/dma/Kconfig                   |   2 +
 drivers/dma/Makefile                  |   1 +
 drivers/dma/ae4dma/Kconfig            |  13 ++
 drivers/dma/ae4dma/Makefile           |  10 +
 drivers/dma/ae4dma/ae4dma-debugfs.c   |  98 ++++++++
 drivers/dma/ae4dma/ae4dma-dev.c       | 353 ++++++++++++++++++++++++++++
 drivers/dma/ae4dma/ae4dma-dmaengine.c | 425 ++++++++++++++++++++++++++++++++++
 drivers/dma/ae4dma/ae4dma-pci.c       | 247 ++++++++++++++++++++
 drivers/dma/ae4dma/ae4dma.h           | 374 ++++++++++++++++++++++++++++++
 10 files changed, 1529 insertions(+)
 create mode 100644 drivers/dma/ae4dma/Kconfig
 create mode 100644 drivers/dma/ae4dma/Makefile
 create mode 100644 drivers/dma/ae4dma/ae4dma-debugfs.c
 create mode 100644 drivers/dma/ae4dma/ae4dma-dev.c
 create mode 100644 drivers/dma/ae4dma/ae4dma-dmaengine.c
 create mode 100644 drivers/dma/ae4dma/ae4dma-pci.c
 create mode 100644 drivers/dma/ae4dma/ae4dma.h

-- 
2.7.4


             reply	other threads:[~2023-09-11 22:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 19:25 Sanjay R Mehta [this message]
2023-09-11 19:25 ` [PATCH 1/3] dmaengine: ae4dma: Initial ae4dma controller driver with multi channel Sanjay R Mehta
2023-10-04  9:54   ` Vinod Koul
2023-10-14  8:26     ` Mehta, Sanju
2023-10-16  6:45       ` Vinod Koul
2023-10-23 15:04         ` Mehta, Sanju
2023-09-11 19:25 ` [PATCH 2/3] dmaengine: ae4dma: register AE4DMA controller as a DMA resource Sanjay R Mehta
2023-10-04 12:47   ` Vinod Koul
2023-10-14  9:14     ` Mehta, Sanju
2023-09-11 19:25 ` [PATCH 3/3] dmaengine: ae4dma: Add debugfs entries for AE4DMA Sanjay R Mehta

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=1694460324-60346-1-git-send-email-Sanju.Mehta@amd.com \
    --to=sanju.mehta@amd.com \
    --cc=dan.j.williams@intel.com \
    --cc=davem@davemloft.net \
    --cc=dmaengine@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=robh@kernel.org \
    --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