Message ID | e0e3cb4ea8b6f2d08e8d07a2ad3b25a2dca4570e.camel@redhat.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | [PULL] topic/amdgpu-dp2.0-mst | expand |
Hi Lyude, On Mon, Oct 25, 2021 at 09:30:14PM -0400, Lyude Paul wrote: > topic/amdgpu-dp2.0-mst-2021-10-25: > UAPI Changes: > Nope! > > Cross-subsystem Changes: > drm_dp_update_payload_part1() takes a new argument for specifying what the > VCPI slot start is > > Core Changes: > Make the DP MST helpers aware of the current starting VCPI slot/VCPI total > slot count... > > Driver Changes: > ...and then add support for taking advantage of this for 128b/132b links on DP > 2.0 for amdgpu It's not really clear to me what branch it should be pulled in? is it for drm-misc-next? Thanks! Maxime
This was for airlied to pull into drm-next On Wed, 2021-10-27 at 09:18 +0200, Maxime Ripard wrote: > Hi Lyude, > > On Mon, Oct 25, 2021 at 09:30:14PM -0400, Lyude Paul wrote: > > topic/amdgpu-dp2.0-mst-2021-10-25: > > UAPI Changes: > > Nope! > > > > Cross-subsystem Changes: > > drm_dp_update_payload_part1() takes a new argument for specifying what the > > VCPI slot start is > > > > Core Changes: > > Make the DP MST helpers aware of the current starting VCPI slot/VCPI total > > slot count... > > > > Driver Changes: > > ...and then add support for taking advantage of this for 128b/132b links > > on DP > > 2.0 for amdgpu > > It's not really clear to me what branch it should be pulled in? is it > for drm-misc-next? > > Thanks! > Maxime