From: pebolle@tiscali.nl (Paul Bolle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 3/5] dmaengine: pxa: add pxa dmaengine driver
Date: Wed, 27 May 2015 08:55:23 +0200 [thread overview]
Message-ID: <1432709723.27695.210.camel@x220> (raw)
In-Reply-To: <87siaizguz.fsf@belgarion.home>
On Wed, 2015-05-27 at 08:15 +0200, Robert Jarzmik wrote:
> Paul Bolle <pebolle@tiscali.nl> writes:
> > Was it actually intended for PXA_DMA to be tristate?
> It is designed to be a module, and in the "end" it will be a module.
>
> What is important to understand is the 3 phases which are going to happen :
> - phase 1 : state after this is merged
> pxa_dma must be builtin, for legacy support (see
> pxad_toggle_reserved_channel()).
> - phase 2 : slowly, all the pxa drivers are converted to dmaengine
> - phase 3 : after full conversion, the patch "add support for legacy
> transition" is reverted.
> There pxa_dma will become modular, and the tristate will appear.
>
> In conclusion, it cannot be a module yet, but it will in the future.
Thanks for this explanation. So I didn't miss a comment or some remark
in a commit explanation, did I?
Paul Bolle
next prev parent reply other threads:[~2015-05-27 6:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 21:29 [PATCH v4 1/5] Documentation: dmaengine: pxa-dma design Robert Jarzmik
2015-05-25 21:29 ` [PATCH v4 2/5] MAINTAINERS: add pxa dma driver to pxa architecture Robert Jarzmik
2015-05-25 21:29 ` [PATCH v4 3/5] dmaengine: pxa: add pxa dmaengine driver Robert Jarzmik
2015-05-26 7:28 ` Paul Bolle
2015-05-27 6:15 ` Robert Jarzmik
2015-05-27 6:55 ` Paul Bolle [this message]
2015-05-27 19:34 ` Robert Jarzmik
2015-05-25 21:29 ` [PATCH v4 4/5] dmaengine: pxa_dma: add debug information Robert Jarzmik
2015-05-25 21:29 ` [PATCH v4 5/5] dmaengine: pxa_dma: add support for legacy transition Robert Jarzmik
2015-05-26 3:48 ` [PATCH v4 1/5] Documentation: dmaengine: pxa-dma design Vinod Koul
2015-05-26 6:12 ` Robert Jarzmik
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=1432709723.27695.210.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).