[PATCH 1/2] mm: cma: export functions to get CMA base and size

[Christoph Hellwig]

On Wed, May 29, 2019 at 12:43:11PM +0200, Lucas Stach wrote:
> Make them usable in modules. Some drivers want to know where their
> device CMA area is located to make better decisions about the DMA
> programming.

NAK.  This is very much a layering violation.  At very least you'd
need to wire this up through the DMA API and deal with dma_addr_t
addresses instead of physical addresses, which are opaque to DMA
using drivers.  But even for that we'd need a really good rationale.