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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 27 May 2015 08:55:23 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Robert Jarzmik <robert.jarzmik@...e.fr>
Cc:	Vinod Koul <vinod.koul@...el.com>,
	Jonathan Corbet <corbet@....net>,
	Daniel Mack <daniel@...que.org>,
	Haojian Zhuang <haojian.zhuang@...il.com>,
	dmaengine@...r.kernel.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v4 3/5] dmaengine: pxa: add pxa dmaengine driver

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/