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>

diff --git a/sound/pci/asihpi/hpios.c b/sound/pci/asihpi/hpios.c
index 5ef4fe964366e6e1c69d9cc71b7794e866ca0a6a..7c91330af7192e3733304d3229c1a4edc080ff18 100644 (file)
--- 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",