diff options
author | Daniel Vetter <daniel.vetter@ffwll.ch> | 2023-03-29 16:45:37 +0300 |
---|---|---|
committer | Daniel Vetter <daniel.vetter@ffwll.ch> | 2023-03-29 16:45:38 +0300 |
commit | 929ae7c2e3adbbb2c2bddcd16854a6b11b56e95a (patch) | |
tree | f023b52847e7f71ad12eedb157f0d7aa77753b92 /drivers/gpu/drm/meson/meson_drv.c | |
parent | 2fcc1fa5f906872f4d3da3fef08fa062fa70a645 (diff) | |
parent | d39e48ca80c0960b039cb38633957f0040f63e1a (diff) | |
download | linux-929ae7c2e3adbbb2c2bddcd16854a6b11b56e95a.tar.xz |
Merge tag 'dma-fence-deadline' of https://gitlab.freedesktop.org/drm/msm into drm-next
This series adds a deadline hint to fences, so realtime deadlines
such as vblank can be communicated to the fence signaller for power/
frequency management decisions.
This is partially inspired by a trick i915 does, but implemented
via dma-fence for a couple of reasons:
1) To continue to be able to use the atomic helpers
2) To support cases where display and gpu are different drivers
See https://patchwork.freedesktop.org/series/93035/
This does not yet add any UAPI, although this will be needed in
a number of cases:
1) Workloads "ping-ponging" between CPU and GPU, where we don't
want the GPU freq governor to interpret time stalled waiting
for GPU as "idle" time
2) Cases where the compositor is waiting for fences to be signaled
before issuing the atomic ioctl, for example to maintain 60fps
cursor updates even when the GPU is not able to maintain that
framerate.
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
From: Rob Clark <robdclark@gmail.com>
Link: https://patchwork.freedesktop.org/patch/msgid/CAF6AEGt5nDQpa6J86V1oFKPA30YcJzPhAVpmF7N1K1g2N3c=Zg@mail.gmail.com
Diffstat (limited to 'drivers/gpu/drm/meson/meson_drv.c')
0 files changed, 0 insertions, 0 deletions