[AMD Official Use Only - General]
> -Original Message-
> From: Lyude Paul
> Sent: Wednesday, May 11, 2022 6:14 AM
> To: Lin, Wayne ; Zuo, Jerry ;
> Wentland, Harry ; amd-
> g...@lists.freedesktop.org
> Subject: Re: Do we really need to increase/decrease MST VC
On Thu, 2022-05-05 at 10:02 +, Lin, Wayne wrote:
>
> I think this shouldn't happen. Please refer to the figure 2-98 of DP spec
> 1.4.
> The payload id table should be changed to below I think.
>
> |1 1 1 2 3 3 X X|
>
> I skimmed over a bit of the implementation in drm. I think it
[Public]
Hi Lyude,
Thanks for raising this!
Please see my comments inline : )
> From: Zuo, Jerry
> Sent: Thursday, May 5, 2022 10:30
> To: Lyude Paul; Lin, Wayne; Wentland, Harry; amd-gfx@lists.freedesktop.org
> Subject: RE: Do we really need
.
Regards,
Jerry
> -Original Message-
> From: Lyude Paul
> Sent: Wednesday, May 4, 2022 5:17 PM
> To: Lin, Wayne ; Wentland, Harry
> ; amd-gfx@lists.freedesktop.org; Zuo, Jerry
>
> Subject: Re: Do we really need to increase/decrease MST VC payloads?
>
> Some go
Some good news: I actually came up with a way of handling this in the new MST
code pretty nicely, so I think we should be able to move forward without
having to disable this (although it would be very nice to know whether or not
this is necessary for amdgpu to work, since it'd still be nice to
Hi! So I kinda hate to ask this, but finding this in amdgpu completely took me
by surprise and unfortunately is (while technically correct) an enormous pain
and not really necessary as far as I'm aware.
So: it seems that amdgpu is currently the only driver that not only
allocates/deallocates
