aboutsummaryrefslogtreecommitdiff
path: root/sound/pci/asihpi
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2018-10-13 17:17:03 +0200
committerTakashi Iwai <tiwai@suse.de>2018-10-14 09:40:24 +0200
commit23fdf223bbe4bd42bbb3f0f5b9d5e64a58956ef7 (patch)
tree9e94eef8c9bbdc7a6638acc851074f75a941a979 /sound/pci/asihpi
parent68da4fa51af4ea9d10099e48351b3cdaae7b1d23 (diff)
downloadlinux-stericsson-23fdf223bbe4bd42bbb3f0f5b9d5e64a58956ef7.tar.gz
ALSA: asihpi: don't pass GFP_DMA32 to dma_alloc_coherent
The DMA API does its own zone decisions based on the coherent_dma_mask. [ Note: as the driver doesn't set the DMA coherent mask, we can assume the default 32bit DMA, hence it should be safe to drop the flag here -- tiwai ] Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Takashi Iwai <tiwai@suse.de>
Diffstat (limited to 'sound/pci/asihpi')
-rw-r--r--sound/pci/asihpi/hpios.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sound/pci/asihpi/hpios.c b/sound/pci/asihpi/hpios.c
index 5ef4fe964366..7c91330af719 100644
--- a/sound/pci/asihpi/hpios.c
+++ b/sound/pci/asihpi/hpios.c
@@ -49,7 +49,7 @@ u16 hpios_locked_mem_alloc(struct consistent_dma_area *p_mem_area, u32 size,
/*?? any benefit in using managed dmam_alloc_coherent? */
p_mem_area->vaddr =
dma_alloc_coherent(&pdev->dev, size, &p_mem_area->dma_handle,
- GFP_DMA32 | GFP_KERNEL);
+ GFP_KERNEL);
if (p_mem_area->vaddr) {
HPI_DEBUG_LOG(DEBUG, "allocated %d bytes, dma 0x%x vma %p\n",