summaryrefslogtreecommitdiffstats
path: root/drivers/android
diff options
context:
space:
mode:
authorFurquan Shaikh <furquan@google.com>2020-10-22 00:15:50 -0700
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-11-09 18:48:06 +0100
commit17adb469bf1ef3c62e9356ab84449df6cad28ed5 (patch)
treed9086dc76c7b9a38440433bc5db170ca698accff /drivers/android
parent88f6c77927e4aee04e0193fd94e13a55753a72b0 (diff)
downloadlinux-stable-17adb469bf1ef3c62e9356ab84449df6cad28ed5.tar.gz
linux-stable-17adb469bf1ef3c62e9356ab84449df6cad28ed5.tar.bz2
linux-stable-17adb469bf1ef3c62e9356ab84449df6cad28ed5.zip
firmware: gsmi: Drop the use of dma_pool_* API functions
GSMI driver uses dma_pool_* API functions for buffer allocation because it requires that the SMI buffers are allocated within 32-bit physical address space. However, this does not work well with IOMMU since there is no real device and hence no domain associated with the device. Since this is not a real device, it does not require any device address(IOVA) for the buffer allocations. The only requirement is to ensure that the physical address allocated to the buffer is within 32-bit physical address space. This is because the buffers have nothing to do with DMA at all. It is required for communication with firmware executing in SMI mode which has access only to the bottom 4GiB of memory. Hence, this change switches to using a SLAB cache created with SLAB_CACHE_DMA32 that guarantees that the allocation happens from the DMA32 memory zone. All calls to dma_pool_* are replaced with kmem_cache_*. In addition to that, all the code for managing the dma_pool for GSMI platform device is dropped. Signed-off-by: Furquan Shaikh <furquan@google.com> Reviewed-by: Ard Biesheuvel <ardb@kernel.org> Link: https://lore.kernel.org/r/20201022071550.1192947-1-furquan@google.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/android')
0 files changed, 0 insertions, 0 deletions