linux-dev - Linux kernel development work

Age	Commit message (Collapse)	Author	Files	Lines
2019-10-30	dma-mapping: fix handling of dma-ranges for reserved memory (again)	Vladimir Murzin	1	-7/+9
	Daniele reported that issue previously fixed in c41f9ea998f3 ("drivers: dma-coherent: Account dma_pfn_offset when used with device tree") reappear shortly after 43fc509c3efb ("dma-coherent: introduce interface for default DMA pool") where fix was accidentally dropped. Lets put fix back in place and respect dma-ranges for reserved memory. Fixes: 43fc509c3efb ("dma-coherent: introduce interface for default DMA pool") Reported-by: Daniele Alessandrelli <daniele.alessandrelli@gmail.com> Tested-by: Daniele Alessandrelli <daniele.alessandrelli@gmail.com> Tested-by: Alexandre Torgue <alexandre.torgue@st.com> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com> Signed-off-by: Christoph Hellwig <hch@lst.de>
2019-09-04	dma-mapping: remove the dma_declare_coherent_memory export	Christoph Hellwig	1	-1/+0
	dma_declare_coherent_memory is something that the platform setup code (which pretty much means the device tree these days) need to do so that drivers can use the memory as declared by the platform. Drivers themselves have no business calling this function. Signed-off-by: Christoph Hellwig <hch@lst.de>
2019-09-04	dma-mapping: remove the dma_mmap_from_dev_coherent export	Christoph Hellwig	1	-1/+0
	dma_mmap_from_dev_coherent is only used by dma_map_ops instances, none of which is modular. Signed-off-by: Christoph Hellwig <hch@lst.de>
2019-09-04	dma-mapping: remove dma_release_declared_memory	Christoph Hellwig	1	-11/+0
	This function is entirely unused given that declared memory is generally provided by platform setup code. Signed-off-by: Christoph Hellwig <hch@lst.de>
2019-02-20	dma-mapping: remove the DMA_MEMORY_EXCLUSIVE flag	Christoph Hellwig	1	-18/+7
	All users of dma_declare_coherent want their allocations to be exclusive, so default to exclusive allocations. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2019-02-20	dma-mapping: remove dma_mark_declared_memory_occupied	Christoph Hellwig	1	-23/+0
	This API is not used anywhere, so remove it. Signed-off-by: Christoph Hellwig <hch@lst.de>
2019-02-13	dma-mapping: remove an incorrect __iommem annotation	Christoph Hellwig	1	-1/+1
	memmap return a regular void pointer, not and __iomem one. Signed-off-by: Christoph Hellwig <hch@lst.de>
2019-01-04	dma-mapping: remove a few unused exports	Christoph Hellwig	1	-2/+0
	Now that the slow path DMA API calls are implemented out of line a few helpers only used by them don't need to be exported anymore. Signed-off-by: Christoph Hellwig <hch@lst.de>
2018-06-14	dma-mapping: move all DMA mapping code to kernel/dma	Christoph Hellwig	1	-0/+434
	Currently the code is split over various files with dma- prefixes in the lib/ and drives/base directories, and the number of files keeps growing. Move them into a single directory to keep the code together and remove the file name prefixes. To match the irq infrastructure this directory is placed under the kernel/ directory. Signed-off-by: Christoph Hellwig <hch@lst.de>