diff options
| author | Ben Skeggs <bskeggs@redhat.com> | 2017-05-19 23:59:35 +1000 |
|---|---|---|
| committer | Ben Skeggs <bskeggs@redhat.com> | 2017-06-16 14:04:57 +1000 |
| commit | 6c22ea3747fd36409ce4a1e1a0cbac40f93e1e71 (patch) | |
| tree | 3e59368a13cff78bed2206404138b0849b56c69d /drivers/gpu/drm/drm_memory.c | |
| parent | 3c66c87dc96b3113b5ee84604800c2aabbb48994 (diff) | |
| download | talos-op-linux-6c22ea3747fd36409ce4a1e1a0cbac40f93e1e71.tar.gz talos-op-linux-6c22ea3747fd36409ce4a1e1a0cbac40f93e1e71.zip | |
drm/nouveau/disp: introduce acquire/release display path methods
These exist to give NVKM information on the set of display paths that
the DD needs to be active at any given time.
Previously, the supervisor attempted to determine this solely from OR
state, but there's a few configurations where this information on its
own isn't enough to determine the specific display paths in question:
- ANX9805, where the PIOR protocol for both DP and TMDS is TMDS.
- On a device using DCB Switched Outputs.
- On GM20x and newer, with a crossbar between the SOR and macro links.
After this commit, the DD tells NVKM *exactly* which display path it's
attempting a modeset on.
Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Diffstat (limited to 'drivers/gpu/drm/drm_memory.c')
0 files changed, 0 insertions, 0 deletions
