public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Laxman Dewangan <ldewangan@nvidia.com>,
	Vinod Koul <vinod.koul@intel.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	Alexandre Courbot <gnurou@gmail.com>
Cc: <dmaengine@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
	Jon Hunter <jonathanh@nvidia.com>
Subject: [RFC PATCH 0/7] DMA: Add support for Tegra210 ADMA
Date: Tue, 18 Aug 2015 14:49:08 +0100	[thread overview]
Message-ID: <1439905755-25150-1-git-send-email-jonathanh@nvidia.com> (raw)

Add support for Tegra210 Audio DMA (ADMA) controller. This driver is based
upon the existing Tegra20-APB DMA driver and a lot of the core code has
been re-used.

This is currently being distributed as an RFC to get feedback on the
approach and although this has been compile and boot tested, it still
needs further functional testing to ensure it is working well.

This series is based upon the Tegra-APB clean-up series [0].

[0] https://lkml.org/lkml/2015/8/6/315

Jon Hunter (7):
  DMA: tegra-apb: Correct runtime-pm usage
  DMA: tegra-apb: Move code dealing with h/w registers into separate
    functions
  DMA: tegra-apb: Clean-up and simplify setting up of transfer
    parameters
  DMA: tegra-apb: Add a function table for functions dealing with
    registers
  DMA: tegra-apb: Move common code into separate source files
  Documentation: DT: Add binding documentation for NVIDIA ADMA
  DMA: tegra-adma: Add support for Tegra210 ADMA

 .../devicetree/bindings/dma/tegra210-adma.txt      |   49 +
 drivers/dma/Kconfig                                |   16 +
 drivers/dma/Makefile                               |    2 +
 drivers/dma/tegra-common.c                         |  734 +++++++++++++
 drivers/dma/tegra-common.h                         |  260 +++++
 drivers/dma/tegra20-apb-dma.c                      | 1121 +++-----------------
 drivers/dma/tegra210-adma.c                        |  710 +++++++++++++
 7 files changed, 1928 insertions(+), 964 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/dma/tegra210-adma.txt
 create mode 100644 drivers/dma/tegra-common.c
 create mode 100644 drivers/dma/tegra-common.h
 create mode 100644 drivers/dma/tegra210-adma.c

-- 
2.1.4


             reply	other threads:[~2015-08-18 13:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 13:49 Jon Hunter [this message]
2015-08-18 13:49 ` [RFC PATCH 1/7] DMA: tegra-apb: Correct runtime-pm usage Jon Hunter
2015-08-23 14:17   ` Vinod Koul
2015-08-24  8:47     ` Jon Hunter
2015-08-24  9:22       ` Vinod Koul
2015-08-24 13:22         ` Jon Hunter
2015-08-24 14:21           ` Vinod Koul
2015-08-25  0:04             ` Rafael J. Wysocki
2015-08-25  9:37               ` Jon Hunter
2015-08-25 22:46                 ` Rafael J. Wysocki
2015-08-28 10:30                   ` Jon Hunter
2015-08-18 13:49 ` [RFC PATCH 2/7] DMA: tegra-apb: Move code dealing with h/w registers into separate functions Jon Hunter
2015-08-18 13:49 ` [RFC PATCH 3/7] DMA: tegra-apb: Clean-up and simplify setting up of transfer parameters Jon Hunter
2015-08-18 13:49 ` [RFC PATCH 4/7] DMA: tegra-apb: Add a function table for functions dealing with registers Jon Hunter
2015-08-18 13:49 ` [RFC PATCH 5/7] DMA: tegra-apb: Move common code into separate source files Jon Hunter
2015-08-18 13:49 ` [RFC PATCH 6/7] Documentation: DT: Add binding documentation for NVIDIA ADMA Jon Hunter
2015-08-18 13:49 ` [RFC PATCH 7/7] DMA: tegra-adma: Add support for Tegra210 ADMA Jon Hunter
2015-08-23 14:33   ` Vinod Koul
2015-08-24  8:55     ` Jon Hunter
2015-08-24  9:24       ` Vinod Koul

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=1439905755-25150-1-git-send-email-jonathanh@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=gnurou@gmail.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=swarren@wwwdotorg.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