gpu: ion: Explictly mark DMA allocations as GFP_KERNEL

For legacy reasons, the GFP allocation for dma allocations is currently
marked as 0, which corresponds to atomic allocations. These allocations
should not be marked as atomic since the atomic pool is very small.
Switch to properly using GFP_KERNEL to always allocate from the
correct pool.

Change-Id: Id3ce68b538a3d6dbdc8857109cca9ec8706ca4ef
Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
misc: pmem: Manage DMA allocation failures

If the system fails to allocate the DMA buffer, to avoid kernel panics,
exit the function returning -1.
misc: pmem: Explictly mark DMA allocations as GFP_KERNEL

As already applied on ion_cma_heap:
https://www.codeaurora.org/cgit/quic/la/kernel/msm/commit/drivers/gpu/ion?h=kk_3.5&id=83062cf0351637afc7c20456a43ac9b12ffab28b

For legacy reasons, the GFP allocation for dma allocations is currently
marked as 0, which corresponds to atomic allocations. These allocations
should not be marked as atomic since the atomic pool is very small.
Switch to properly using GFP_KERNEL to always allocate from the
correct pool.
block: bfq: Squashed update from BFQ-v7r4 to BFQ-v7r5

Change-Id: I749ef141246db7020cec0b10d980ec854a572603