diff options
| author | Lyude Paul <lyude@redhat.com> | 2018-09-17 20:37:33 +0300 |
|---|---|---|
| committer | Lyude Paul <lyude@redhat.com> | 2018-09-18 02:24:37 +0300 |
| commit | 3c499ea0c662e2f38aafbd4f516b08aab8cfa0e5 (patch) | |
| tree | 71fcdb65993bde73abd9c8746ea7d4bb7e6ff073 /include | |
| parent | 6ee67e351cdae68b4c9c7df74124b9f9fb81e966 (diff) | |
| download | linux-3c499ea0c662e2f38aafbd4f516b08aab8cfa0e5.tar.xz | |
drm/atomic: Use drm_drv_uses_atomic_modeset() for debugfs creation
As pointed out by Daniel Vetter, we should be usinng
drm_drv_uses_atomic_modeset() for determining whether or not we want to
make the debugfs nodes for atomic instead of checking DRIVER_ATOMIC, as
the former isn't an accurate representation of whether or not the driver
is actually using atomic modesetting internally (even though it might
not be exposing atomic capabilities).
Signed-off-by: Lyude Paul <lyude@redhat.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: stable@vger.kernel.org
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Link: https://patchwork.freedesktop.org/patch/msgid/20180917173733.21293-1-lyude@redhat.com
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions