Re: cleanup the dma_pgprot handling v2

2019-08-29 Thread Christoph Hellwig
I've pulled this into the dma-mapping for-next tree now.

cleanup the dma_pgprot handling v2

2019-08-26 Thread Christoph Hellwig
Hi all, this series replaces the arch_dma_mmap_pgprot hooks with the simpler pgprot_dmacoherent as used by the arm code already and cleans up various bits around that area. Changes since v1: - improve the new arm64 comment - keep the special DMA_ATTR_WRITE_COMBINE handling for mips and

Re: cleanup the dma_pgprot handling

2019-08-24 Thread Christoph Hellwig
On Fri, Aug 23, 2019 at 09:58:04PM +, Paul Burton wrote: > So I believe uncached & uncached accelerated are another case like that > described above - they're 2 different CCAs but the same "access type", > namely uncached. > > Section 4.9 then goes on to forbid mixing access types, but not

Re: cleanup the dma_pgprot handling

2019-08-23 Thread Paul Burton
Hi Christoph, On Fri, Aug 16, 2019 at 09:07:48AM +0200, Christoph Hellwig wrote: > I'd still like to hear a confirmation from the mips folks how > the write combibe attribute can or can't work with the KSEG1 > uncached segment. Quoting section 4.8 "Cacheability and Coherency Attributes and

cleanup the dma_pgprot handling

2019-08-16 Thread Christoph Hellwig
Hi all, this series replaced the arch_dma_mmap_pgprot hooks with the simpler pgprot_dmacoherent as used by the arm code already and cleans up various bits around that area. I'd still like to hear a confirmation from the mips folks how the write combibe attribute can or can't work with the KSEG1