summaryrefslogtreecommitdiff
path: root/drivers/nvmem
diff options
context:
space:
mode:
authorGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-05-25 08:49:43 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-05-25 08:49:43 +0200
commit18cbc336ec1a640ef4e62107d627bf1cf26ac6b9 (patch)
treefc7ae7c7cae4bfda1d96d9fc075d61414980a011 /drivers/nvmem
parent709b41b56a16a5901a89dcaeb75d2233f80d9e55 (diff)
parent8ff5f4fd40df9525675ea0e512da4cec65d646eb (diff)
Merge tag 'misc-habanalabs-next-2020-05-25' of git://people.freedesktop.org/~gabbayo/linux into char-misc-next
Oded writes: This tag contains the following changes for kernel 5.8: - Improve MMU cache invalidation code and handle case where the invalidation doesn't finish in a reasonable time. - Remove the option to perform soft-reset to GAUDI. Soft-reset is where the driver only resets the compute and DMA engines of the ASIC. This is not relevant to GAUDI as we must also reset the NIC ports. And when we reset the NIC ports, we must also reset other stuff so we prefer to just do hard-reset (where we reset the entire ASIC except for PCIe). - Fail the hard-reset procedure in case we still have user processes which have active file-descriptors on a device. Doing hard-reset in that case can result in a kernel panic because of gen_pool checks - Don't initialize the default wait callback of dma_buf with the default wait function as that's the default... * tag 'misc-habanalabs-next-2020-05-25' of git://people.freedesktop.org/~gabbayo/linux: habanalabs: handle MMU cache invalidation timeout habanalabs: don't allow hard reset with open processes habanalabs: GAUDI does not support soft-reset habanalabs: add print for soft reset due to event habanalabs: improve MMU cache invalidation code habanalabs: don't set default fence_ops->wait
Diffstat (limited to 'drivers/nvmem')
0 files changed, 0 insertions, 0 deletions