From: Robert Jarzmik <robert.jarzmik@free.fr> To: Vinod Koul <vinod.koul@intel.com>, Jonathan Corbet <corbet@lwn.net>, Daniel Mack <daniel@zonque.org>, Haojian Zhuang <haojian.zhuang@gmail.com>, Robert Jarzmik <robert.jarzmik@free.fr> Cc: dmaengine@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/5] Driver for pxa architectures Date: Sat, 21 Mar 2015 23:44:23 +0100 [thread overview] Message-ID: <1426977868-5414-1-git-send-email-robert.jarzmik@free.fr> (raw) Hi Vinod, This serie introduces a new driver for Marvell pxa architectures. There is a full rationale explanation in patch 3/5 on why mmp_pdma was not reused nor patched incrementally. This new driver provides all the capabilities to port all the drivers of pxa architecture to dmaengine. It was tested against the most dma advanced user I know (pxa_camera), as well a more casual ones (pxamci and dmatest). This is big piece of code, so I expect the review will take time. If we converge on it, it will be maintained as well as part of the pxa architeture maintainance. It is as well one of the last steps (or so I hope) for pxa architure to be part of the multiplatform ARM architecture, and at the same time keep its legacy platforms operational. It will kill arch/arm/plat-pxa/dma.c in the long term. Cheers. -- Robert Robert Jarzmik (5): Documentation: dmaengine: pxa-dma design MAINTAINERS: add pxa dma driver to pxa architecture dmaengine: pxa: add pxa dmaengine driver dmaengine: pxa_dma: add debug information dmaengine: pxa_dma: add support for legacy transition Documentation/dmaengine/pxa_dma.txt | 157 ++++ MAINTAINERS | 1 + drivers/dma/Kconfig | 11 + drivers/dma/Makefile | 1 + drivers/dma/pxa_dma.c | 1475 +++++++++++++++++++++++++++++++++++ include/linux/dma/pxa-dma.h | 27 + 6 files changed, 1672 insertions(+) create mode 100644 Documentation/dmaengine/pxa_dma.txt create mode 100644 drivers/dma/pxa_dma.c create mode 100644 include/linux/dma/pxa-dma.h -- 2.1.4
WARNING: multiple messages have this Message-ID (diff)
From: robert.jarzmik@free.fr (Robert Jarzmik) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH 0/5] Driver for pxa architectures Date: Sat, 21 Mar 2015 23:44:23 +0100 [thread overview] Message-ID: <1426977868-5414-1-git-send-email-robert.jarzmik@free.fr> (raw) Hi Vinod, This serie introduces a new driver for Marvell pxa architectures. There is a full rationale explanation in patch 3/5 on why mmp_pdma was not reused nor patched incrementally. This new driver provides all the capabilities to port all the drivers of pxa architecture to dmaengine. It was tested against the most dma advanced user I know (pxa_camera), as well a more casual ones (pxamci and dmatest). This is big piece of code, so I expect the review will take time. If we converge on it, it will be maintained as well as part of the pxa architeture maintainance. It is as well one of the last steps (or so I hope) for pxa architure to be part of the multiplatform ARM architecture, and at the same time keep its legacy platforms operational. It will kill arch/arm/plat-pxa/dma.c in the long term. Cheers. -- Robert Robert Jarzmik (5): Documentation: dmaengine: pxa-dma design MAINTAINERS: add pxa dma driver to pxa architecture dmaengine: pxa: add pxa dmaengine driver dmaengine: pxa_dma: add debug information dmaengine: pxa_dma: add support for legacy transition Documentation/dmaengine/pxa_dma.txt | 157 ++++ MAINTAINERS | 1 + drivers/dma/Kconfig | 11 + drivers/dma/Makefile | 1 + drivers/dma/pxa_dma.c | 1475 +++++++++++++++++++++++++++++++++++ include/linux/dma/pxa-dma.h | 27 + 6 files changed, 1672 insertions(+) create mode 100644 Documentation/dmaengine/pxa_dma.txt create mode 100644 drivers/dma/pxa_dma.c create mode 100644 include/linux/dma/pxa-dma.h -- 2.1.4
next reply other threads:[~2015-03-21 22:50 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-21 22:44 Robert Jarzmik [this message] 2015-03-21 22:44 ` [PATCH 0/5] Driver for pxa architectures Robert Jarzmik 2015-03-21 22:44 ` [PATCH 1/5] Documentation: dmaengine: pxa-dma design Robert Jarzmik 2015-03-21 22:44 ` Robert Jarzmik 2015-03-21 22:44 ` [PATCH 2/5] MAINTAINERS: add pxa dma driver to pxa architecture Robert Jarzmik 2015-03-21 22:44 ` Robert Jarzmik 2015-03-21 22:44 ` [PATCH 3/5] dmaengine: pxa: add pxa dmaengine driver Robert Jarzmik 2015-03-21 22:44 ` Robert Jarzmik 2015-04-02 9:06 ` Robert Jarzmik 2015-04-02 9:06 ` Robert Jarzmik 2015-04-02 10:46 ` Vinod Koul 2015-04-02 10:46 ` Vinod Koul 2015-03-21 22:44 ` [PATCH 4/5] dmaengine: pxa_dma: add debug information Robert Jarzmik 2015-03-21 22:44 ` Robert Jarzmik 2015-03-21 22:44 ` [PATCH 5/5] dmaengine: pxa_dma: add support for legacy transition Robert Jarzmik 2015-03-21 22:44 ` Robert Jarzmik 2015-03-22 2:20 ` [PATCH 0/5] Driver for pxa architectures Arnd Bergmann 2015-03-22 2:20 ` Arnd Bergmann 2015-03-23 9:21 ` Robert Jarzmik 2015-03-23 9:21 ` Robert Jarzmik 2015-03-23 15:04 ` Arnd Bergmann 2015-03-23 15:04 ` Arnd Bergmann 2015-03-23 20:33 ` Robert Jarzmik 2015-03-23 20:33 ` Robert Jarzmik 2015-03-24 5:17 ` Arnd Bergmann 2015-03-24 5:17 ` Arnd Bergmann
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=1426977868-5414-1-git-send-email-robert.jarzmik@free.fr \ --to=robert.jarzmik@free.fr \ --cc=corbet@lwn.net \ --cc=daniel@zonque.org \ --cc=dmaengine@vger.kernel.org \ --cc=haojian.zhuang@gmail.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --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: linkBe 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.