diff options
| author | Thierry Reding <treding@nvidia.com> | 2019-06-05 10:46:05 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-07-31 07:26:59 +0200 |
| commit | 4d14323a2eb556a9d06d0a956618662bc9dad1c1 (patch) | |
| tree | 59110dde3ffd0516b53f72846ab62f7bec13f990 /include/linux | |
| parent | f9bfd6bd8223b0fccd12d39131a8c6d5d3333cc0 (diff) | |
| download | linux-stable-4d14323a2eb556a9d06d0a956618662bc9dad1c1.tar.gz linux-stable-4d14323a2eb556a9d06d0a956618662bc9dad1c1.tar.bz2 linux-stable-4d14323a2eb556a9d06d0a956618662bc9dad1c1.zip | |
gpu: host1x: Increase maximum DMA segment size
[ Upstream commit 1e390478cfb527e34c9ab89ba57212cb05c33c51 ]
Recent versions of the DMA API debug code have started to warn about
violations of the maximum DMA segment size. This is because the segment
size defaults to 64 KiB, which can easily be exceeded in large buffer
allocations such as used in DRM/KMS for framebuffers.
Technically the Tegra SMMU and ARM SMMU don't have a maximum segment
size (they map individual pages irrespective of whether they are
contiguous or not), so the choice of 4 MiB is a bit arbitrary here. The
maximum segment size is a 32-bit unsigned integer, though, so we can't
set it to the correct maximum size, which would be the size of the
aperture.
Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'include/linux')
| -rw-r--r-- | include/linux/host1x.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/include/linux/host1x.h b/include/linux/host1x.h index 89110d896d72..aef6e2f73802 100644 --- a/include/linux/host1x.h +++ b/include/linux/host1x.h @@ -310,6 +310,8 @@ struct host1x_device { struct list_head clients; bool registered; + + struct device_dma_parameters dma_parms; }; static inline struct host1x_device *to_host1x_device(struct device *dev) |