On Mon, 2014-10-13 at 20:00 +1100, Michael Ellerman wrote:
On Mon, 2014-10-13 at 18:14 +1100, Anton Blanchard wrote:
Hi Scott,
Platform code can call limit_zone_pfn() to set appropriate limits
for ZONE_DMA and ZONE_DMA32, and dma_direct_alloc_coherent() will
select a suitable zone
On Tue, 2014-10-14 at 09:39 +0200, Scott Wood wrote:
For a short-term workaround, I'd rather leave CONFIG_ZONE_DMA32 where
it
is and put #ifdef CONFIG_FSL_SOC (with a comment) around the whole
thing.
I'd like to not enable CONFIG_ZONE_DMA32 when we don't need it, ie,
on !BOOKE 64-bit
Cheers,
On Tue, 2014-10-14 at 18:57 +1100, Benjamin Herrenschmidt wrote:
On Tue, 2014-10-14 at 09:39 +0200, Scott Wood wrote:
For a short-term workaround, I'd rather leave CONFIG_ZONE_DMA32 where
it
is and put #ifdef CONFIG_FSL_SOC (with a comment) around the whole
thing.
I'd like to not
Hi Scott,
Platform code can call limit_zone_pfn() to set appropriate limits
for ZONE_DMA and ZONE_DMA32, and dma_direct_alloc_coherent() will
select a suitable zone based on a device's mask and the pfn limits
that platform code has configured.
This patch breaks my POWER8 box:
ipr
On Mon, 2014-10-13 at 18:14 +1100, Anton Blanchard wrote:
Hi Scott,
Platform code can call limit_zone_pfn() to set appropriate limits
for ZONE_DMA and ZONE_DMA32, and dma_direct_alloc_coherent() will
select a suitable zone based on a device's mask and the pfn limits
that platform code
On Mon, 2014-10-13 at 18:14 +1100, Anton Blanchard wrote:
Hi Scott,
Platform code can call limit_zone_pfn() to set appropriate limits
for ZONE_DMA and ZONE_DMA32, and dma_direct_alloc_coherent() will
select a suitable zone based on a device's mask and the pfn limits
that platform code
Platform code can call limit_zone_pfn() to set appropriate limits
for ZONE_DMA and ZONE_DMA32, and dma_direct_alloc_coherent() will
select a suitable zone based on a device's mask and the pfn limits that
platform code has configured.
Signed-off-by: Scott Wood scottw...@freescale.com
Cc: Shaohui
