Re: [Intel-gfx] [PATCH v2 16/17] drm/i915/dp_mst: Add workaround for a DELL P2715Q payload allocation problem

2023-02-01 Thread Imre Deak
On Tue, Jan 31, 2023 at 05:47:11PM -0500, Lyude Paul wrote: > On Tue, 2023-01-31 at 17:05 +0200, Imre Deak wrote: > > The DELL P2715Q monitor's MST hub has a payload allocation problem, > > LMAO hello yet again, Dell P2715Q. It's been a while. > > > where the VCPI used to reserve the last two

Re: [Intel-gfx] [PATCH v2 16/17] drm/i915/dp_mst: Add workaround for a DELL P2715Q payload allocation problem

2023-01-31 Thread Lyude Paul
I mentioned this once already but: really, I am genuinely impressed at this! I never expected to see this monitor ever work. Also, thank you a ton for adding the payload table verification stuff here. For the whole series: Reviewed-by: Lyude Paul On Tue, 2023-01-31 at 17:05 +0200, Imre Deak

Re: [Intel-gfx] [PATCH v2 16/17] drm/i915/dp_mst: Add workaround for a DELL P2715Q payload allocation problem

2023-01-31 Thread Lyude Paul
On Tue, 2023-01-31 at 17:05 +0200, Imre Deak wrote: > The DELL P2715Q monitor's MST hub has a payload allocation problem, LMAO hello yet again, Dell P2715Q. It's been a while. > where the VCPI used to reserve the last two time slots (at position > 0x3e, 0x3f) in the hub's payload table, this

[Intel-gfx] [PATCH v2 16/17] drm/i915/dp_mst: Add workaround for a DELL P2715Q payload allocation problem

2023-01-31 Thread Imre Deak
The DELL P2715Q monitor's MST hub has a payload allocation problem, where the VCPI used to reserve the last two time slots (at position 0x3e, 0x3f) in the hub's payload table, this VCPI can't be reused for later payload configurations. The problem results at least in streams reusing older VCPIs