aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/generate_rust_analyzer.py
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2023-01-17 14:28:34 +0530
committerBjorn Andersson <andersson@kernel.org>2023-01-18 21:36:17 -0600
commita899d542b687c9b04ccbd9eefabc829ba5fef791 (patch)
tree14217b4e0a01e7fbeb68ee3074974d1fce2740f6 /scripts/generate_rust_analyzer.py
parentdt-bindings: remoteproc: qcom,sc7280-mss-pil: Update memory-region (diff)
downloadlinux-rng-a899d542b687c9b04ccbd9eefabc829ba5fef791.tar.xz
linux-rng-a899d542b687c9b04ccbd9eefabc829ba5fef791.zip
Revert "remoteproc: qcom_q6v5_mss: map/unmap metadata region before/after use"
This reverts commit fc156629b23a21181e473e60341e3a78af25a1d4. This commit manages to do three API violations at once: - dereference the return value of dma_alloc_attrs with the DMA_ATTR_NO_KERNEL_MAPPING mapping, which is clearly forbidden and will do the wrong thing on various dma mapping implementations. The fact that dma-direct uses a struct page as a cookie is an undocumented implementation detail - include dma-map-ops.h and use pgprot_dmacoherent despite a clear comment documenting that this is not acceptable - use of the VM_DMA_COHERENT for something that is not the dma-mapping code - use of VM_FLUSH_RESET_PERMS for vmap, while it is only supported for vmalloc Acked-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org> Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Sibi Sankar <quic_sibis@quicinc.com> Signed-off-by: Bjorn Andersson <andersson@kernel.org> Link: https://lore.kernel.org/r/20230117085840.32356-6-quic_sibis@quicinc.com
Diffstat (limited to 'scripts/generate_rust_analyzer.py')
0 files changed, 0 insertions, 0 deletions