diff options
| author | Ørjan Eide <orjan.eide@arm.com> | 2018-01-30 15:28:33 -0500 |
|---|---|---|
| committer | Heiko Stuebner <heiko@sntech.de> | 2018-02-18 05:16:55 -0500 |
| commit | 57de50af162b67612da99207b061ade3239e57db (patch) | |
| tree | 0487d270d8cf88ee6f49bbe5bc55489e7d59982f /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 6fd0bfe2f7ea1a5828c44b8d8811820bf7be13a9 (diff) | |
drm/rockchip: Respect page offset for PRIME mmap calls
When mapping external DMA-bufs through the PRIME mmap call, we might be
given an offset which has to be respected. However for the internal DRM
GEM mmap path, we have to ignore the fake mmap offset used to identify
the buffer only. Currently the code always zeroes out vma->vm_pgoff,
which breaks the former.
This patch fixes the problem by moving the vm_pgoff assignment to a
function that is used only for GEM mmap path, so that the PRIME path
retains the original offset.
Cc: Daniel Kurtz <djkurtz@chromium.org>
Signed-off-by: Ørjan Eide <orjan.eide@arm.com>
Signed-off-by: Tomasz Figa <tfiga@chromium.org>
Signed-off-by: Sean Paul <seanpaul@chromium.org>
Signed-off-by: Thierry Escande <thierry.escande@collabora.com>
Tested-by: Heiko Stuebner <heiko@sntech.de>
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Link: https://patchwork.freedesktop.org/patch/msgid/20180130202913.28724-4-thierry.escande@collabora.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions