From: Marc Gonzalez <marc_gonzalez@sigmadesigns.com>
To: Mans Rullgard <mans@mansr.com>, Vinod Koul <vinod.koul@intel.com>
Cc: <dmaengine@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Sebastian Frias <sf84@laposte.net>, Mason <slash.tmp@free.fr>,
Thibaud Cornic <thibaud_cornic@sigmadesigns.com>
Subject: Driver for tango DMA engine
Date: Wed, 23 Nov 2016 17:48:10 +0100 [thread overview]
Message-ID: <5835C84A.6000706@sigmadesigns.com> (raw)
Hello Mans,
I would like to push upstream the driver you wrote for the tango
DMA engine. Could you take a look at my fixes, perhaps some/all
can be squashed into the initial patch?
Vinod, can you take a look at this submission, and tell me if
you spot any issue?
Regards.
Mans Rullgard (1):
dmaengine: Import tango MBUS driver
Marc Gonzalez (5):
Provide names for SBOX register offsets
Fixup for tango4 support
Fixup tangox_dma_sbox_map
Fixup tangox_dma_reset
Relax write accesses
drivers/dma/Kconfig | 6 +
drivers/dma/Makefile | 1 +
drivers/dma/tango-dma.c | 582 ++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 589 insertions(+)
create mode 100644 drivers/dma/tango-dma.c
--
2.9.0
next reply other threads:[~2016-11-23 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 16:48 Marc Gonzalez [this message]
2016-11-23 16:49 ` [PATCH 1/6] dmaengine: Import tango MBUS driver Marc Gonzalez
2016-11-23 16:50 ` [PATCH 2/6] Provide names for SBOX register offsets Marc Gonzalez
2016-11-23 16:51 ` [PATCH 3/6] Fixup for tango4 support Marc Gonzalez
2016-11-23 16:51 ` [PATCH 4/6] Fixup tangox_dma_sbox_map Marc Gonzalez
2016-11-23 16:56 ` [PATCH 5/6] Fixup tangox_dma_reset Marc Gonzalez
2016-11-23 16:56 ` [PATCH 6/6] Relax write accesses Marc Gonzalez
2016-11-23 17:27 ` Driver for tango DMA engine Måns Rullgård
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=5835C84A.6000706@sigmadesigns.com \
--to=marc_gonzalez@sigmadesigns.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mans@mansr.com \
--cc=sf84@laposte.net \
--cc=slash.tmp@free.fr \
--cc=thibaud_cornic@sigmadesigns.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