Yes, we've discussed that too...but not come to a conclusion. The problem is
really that if you call dma_alloc and pass in the DMA_CONFORMANCE_NON_CONSISTEN
T flag, what you're saying is "This driver implements all the correct cache
flushes and can cope with inconsistent memory. Please give me the type of
memory that's most efficient for the platform I'm running on.". The driver
isn't asking give me a specific type of memory, it's telling the platform what
it's capabilities are.
Any thoughts on naming would be most welcome.
How about just making a dma_alloc_$(NEWNAME)(), and consistent ports
can just alias that to dma_alloc_consistent()?
The only question is $(NEWNAME). "inconsistent" might be ok, but it's
maybe too similar to "consistent" for my taste.
How about dma_alloc_noncoherent(). I like this one, comments?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/