Christoph Hellwig 3731c3d477 dma-mapping: always build the direct mapping code ... All architectures except for sparc64 use the dma-direct code in some form, and even for sparc64 we had the discussion of a direct mapping mode a while ago. In preparation for directly calling the direct mapping code don't bother having it optionally but always build the code in. This is a minor hardship for some powerpc and arm configs that don't pull it in yet (although they should in a relase ot two), and sparc64 which currently doesn't need it at all, but it will reduce the ifdef mess we'd otherwise need significantly. Signed-off-by: Christoph Hellwig <hch@lst.de> Acked-by: Jesper Dangaard Brouer <brouer@redhat.com> Tested-by: Jesper Dangaard Brouer <brouer@redhat.com> Tested-by: Tony Luck <tony.luck@intel.com>		2018-12-13 21:06:11 +01:00
..
abiv1	csky: Misc headers	2018-10-26 00:54:26 +08:00
abiv2	csky: Misc headers	2018-10-26 00:54:26 +08:00
boot	csky: use common dtb build rules	2018-11-01 10:52:27 +08:00
configs	csky: defconfig	2018-10-25 23:36:19 +08:00
include	treewide: remove current_text_addr	2018-10-31 08:54:12 -07:00
kernel	mm: remove CONFIG_HAVE_MEMBLOCK	2018-10-31 08:54:15 -07:00
lib	csky: User access	2018-10-26 00:54:25 +08:00
mm	csky: use the generic remapping dma alloc implementation	2018-12-01 18:07:16 +01:00
Kconfig	dma-mapping: always build the direct mapping code	2018-12-13 21:06:11 +01:00
Kconfig.debug	csky: remove builtin-dtb Kbuild	2018-11-01 10:52:26 +08:00
Makefile	csky: use common dtb build rules	2018-11-01 10:52:27 +08:00