Re: [PATCH v4 3/5] dmaengine: pxa: add pxa dmaengine driver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2015-05-27 at 08:15 +0200, Robert Jarzmik wrote:
> Paul Bolle <pebolle@xxxxxxxxxx> 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

--
To unsubscribe from this list: send the line "unsubscribe dmaengine" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux PCI]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]     [Yosemite Campsites]

  Powered by Linux