aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/hwmon
diff options
context:
space:
mode:
authorMarek Szyprowski <m.szyprowski@samsung.com>2012-11-07 15:37:07 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-12-17 10:49:02 -0800
commitb9f21c252726e320c3878d9206571e2178cafd10 (patch)
treed989336e97007e541918091852b1f2053aee688d /drivers/hwmon
parent3ff0aeceb49aca3f99c37189e949bf43bfd393a0 (diff)
downloadkernel_samsung_smdk4412-b9f21c252726e320c3878d9206571e2178cafd10.zip
kernel_samsung_smdk4412-b9f21c252726e320c3878d9206571e2178cafd10.tar.gz
kernel_samsung_smdk4412-b9f21c252726e320c3878d9206571e2178cafd10.tar.bz2
mm: dmapool: use provided gfp flags for all dma_alloc_coherent() calls
commit 387870f2d6d679746020fa8e25ef786ff338dc98 upstream. dmapool always calls dma_alloc_coherent() with GFP_ATOMIC flag, regardless the flags provided by the caller. This causes excessive pruning of emergency memory pools without any good reason. Additionaly, on ARM architecture any driver which is using dmapools will sooner or later trigger the following error: "ERROR: 256 KiB atomic DMA coherent pool is too small! Please increase it with coherent_pool= kernel parameter!". Increasing the coherent pool size usually doesn't help much and only delays such error, because all GFP_ATOMIC DMA allocations are always served from the special, very limited memory pool. This patch changes the dmapool code to correctly use gfp flags provided by the dmapool caller. Reported-by: Soeren Moch <smoch@web.de> Reported-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com> Tested-by: Andrew Lunn <andrew@lunn.ch> Tested-by: Soeren Moch <smoch@web.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/hwmon')
0 files changed, 0 insertions, 0 deletions