diff options
author | Lucas Stach <l.stach@pengutronix.de> | 2018-09-12 16:34:27 +0200 |
---|---|---|
committer | Lucas Stach <l.stach@pengutronix.de> | 2018-09-14 18:46:10 +0200 |
commit | 1a866306e0fbf3caab168c1389e4497702749441 (patch) | |
tree | 22b96973ceba55efa9fe31c928e47b3b31243ba7 /fs/affs/symlink.c | |
parent | 5b394b2ddf0347bef56e50c69a58773c94343ff3 (diff) | |
download | linux-1a866306e0fbf3caab168c1389e4497702749441.tar.gz linux-1a866306e0fbf3caab168c1389e4497702749441.tar.bz2 linux-1a866306e0fbf3caab168c1389e4497702749441.zip |
drm/etnaviv: add DMA configuration for etnaviv platform device
The etnaviv device is a virtual device backing the DRM device, which may
drive multiple hardware GPU core devices. As most of the dma-mapping handling
is done through the virtual device, we need to make sure that a proper DMA
setup is in place. The easiest way to get a reasonable configuration is
to let the virtual device share the DMA configuration with one of the GPU
devices, so call of_dma_configure() with the right parameters manually.
This assumes that all etnaviv driven GPU devices in the system share the
same DMA configuration. If we ever encounter a SoC where the GPUs are on
busses with different offsets or behind different IOMMUs that will require
much deeper changes to the driver, as we would need to implement etnaviv
specific versions of most of the DRM helper functions.
For now we should be fine with this solution.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Tested-by: Guido Günther <agx@sigxcpu.org>
Tested-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
Diffstat (limited to 'fs/affs/symlink.c')
0 files changed, 0 insertions, 0 deletions