For example, the HTC Vive Pro 2 VR headset uses this value in
high-resolution modes (3680x1836@90-120, 4896x2448@90-120), and when the
kernel doesn't respect this parameter, garbage is displayed on the HMD
instead.

Me and other users have successfully tested the old (v3) version of this
patch (which was applying DSC BPP value unconditionally, thus incorrect:
https://lkml.org/lkml/2023/2/26/116) on Vive Pro 2 and
Bigscreen Beyond VR headsets, and have been using it daily, it is known
to work and doesn't seem to break anything else since 2022.

Previously, I didn't have enough dedication to get it merged, I hope
this time I will manage to get it to v6.19 :D

Regarding driver support - I have looked at amdgpu and Nvidia's
open-gpu-kernel-modules, and both seem to have some indication for this
value; however, in Linux, it is unused in both.

First patch implements parsing of DSC BPP values and display mode VII
timings flag which mandates that the DSC BPP value should actually be
used for this display mode.

The second patch implements handling of this value for AMDGPU driver.

The only thing that I don't like in the current implementation, is how
the value of `dsc_passthrough_timings_support` flag is propagated from
the connector display modes to the mode created in `DRM_IOCTL_MODE_SETCRTC`
handler (which is used for VR display initialization in Monado and
StreamVR), it feels like this flag should be initialized by the kernel
itself, but as far as I can see there is no correct way to do this, as
the timing constraints calculation belongs to the individual drivers.

Another problem with how this flag is set, is that there is no hard
connection between modes creaded in `SETCRTC` and the modes actually
defined by connector, so the current implementation searches for the
resolution and refresh rate that match exactly declared to obtain
this flag value. This might not be correct, as device might not support
the other mode at all, but the situation won't be any worse for the
existing devices, as the currently they don't work at all, and there
is no other known devices on the market to check their assumption in
regard to this part of specs, and the spec does not describe how that
should work.

Both of those downsides are due to the fact my understanding of DRM
subsystem is not that high. If another implementation would be proposed
by AMDGPU maintainers - I will gladly implement it here.

v5->v6:
 * amdgpu: only apply dsc bpp to modes that match exactly the declared
   modes with this flag set.
v4->v5:
 * The patch was split into multiple
 * Disabled MSO parsing for eDP displays
 * Disabled MSO logs if not used
 * Minor codestyle changes: lines moved around, naming, passing of
   function arguments
v3->v4:
 * This patch now parses timings support flag on type VII block, instead
   of applying it unconditionally. Previously I didn't understand the
   spec properly.
 * Now it also is not being applied for non-supported and/or non-VII
   blocks in amdgpu driver.

Regards,

Lach

Yaroslav Bolyukin (7):
  drm/edid: rename VESA block parsing functions to more generic name
  drm/edid: prepare for VESA vendor-specific data block extension
  drm/edid: MSO should only be used for non-eDP displays
  drm/edid: parse DSC DPP passthru support flag for mode VII timings
  drm/edid: for consistency, use mask everywhere for block rev parsing
  drm/edid: parse DRM VESA dsc bpp target
  drm/amd: use fixed dsc bits-per-pixel from edid

 .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c |  16 +++
 drivers/gpu/drm/drm_displayid_internal.h      |  11 ++
 drivers/gpu/drm/drm_edid.c                    | 101 +++++++++++-------
 include/drm/drm_connector.h                   |   6 ++
 include/drm/drm_modes.h                       |  10 ++
 5 files changed, 107 insertions(+), 37 deletions(-)

-- 
2.51.2

Sorry, I have updated/included the wrong cover message

On 2025-11-26 07:51, Yaroslav Bolyukin wrote:
 > For example, the HTC Vive Pro 2 VR headset uses this value in
 > high-resolution modes (3680x1836@90-120, 4896x2448@90-120), and when the
 > kernel doesn't respect this parameter, garbage is displayed on the HMD
 > instead.
 >
 > Me and other users have successfully tested the old (v3) version of this
 > patch (which was applying DSC BPP value unconditionally, thus incorrect:
 > https://lkml.org/lkml/2023/2/26/116) on Vive Pro 2 and
 > Bigscreen Beyond VR headsets, and have been using it daily, it is known
 > to work and doesn't seem to break anything else since 2022.
 >
 > Previously, I didn't have enough dedication to get it merged, I hope
 > this time I will manage to get it to v6.19 :D
 >
 > Regarding driver support - I have looked at amdgpu and Nvidia's
 > open-gpu-kernel-modules, and both seem to have some indication for this
 > value; however, in Linux, it is unused in both.
 >
 > First patch implements parsing of DSC BPP values and display mode VII
 > timings flag which mandates that the DSC BPP value should actually be
 > used for this display mode.

This patch was split into 1-6

 > The second patch implements handling of this value for AMDGPU driver.

This is the 7th patch

 > The only thing that I don't like in the current implementation, is how
 > the value of `dsc_passthrough_timings_support` flag is propagated from
 > the connector display modes to the mode created in 
`DRM_IOCTL_MODE_SETCRTC`
 > handler (which is used for VR display initialization in Monado and
 > StreamVR), it feels like this flag should be initialized by the kernel
 > itself, but as far as I can see there is no correct way to do this, as
 > the timing constraints calculation belongs to the individual drivers.

This is somewhat improved, now there is a matching for correct mode in
amdgpu driver. I don't like that individual drivers need to repeat this
logic by themselves either, but I don't see a better solution with the
given spec and given how it is implemented in devices. It works more
like a quirk, and the implementation follows. It might be improved if
the future changes in DisplayID spec declare something else DSC related
and the logic would be extended appropriately.

Still, the latest implementation should be easy and descriptive enough
to be easily implementable by the drivers, and given that this part of
spec is only used by ~3 devices on the market right now with both being
VR related, I think this is acceptable.

I have a patch somewhat ready for i915, which I decided to not include
in the current patchset, and I don't think there is more drm drivers
that need this implementation right now (Doesn't seem like anyone runs
VR on nouveau).

Since the first version of the patchset was published, nivida open
drivers have implemented this part by themselves, using their own edid
parser.

 > Another problem with how this flag is set, is that there is no hard
 > connection between modes creaded in `SETCRTC` and the modes actually
 > defined by connector, so the current implementation searches for the
 > resolution and refresh rate that match exactly declared to obtain
 > this flag value. This might not be correct, as device might not support
 > the other mode at all, but the situation won't be any worse for the
 > existing devices, as the currently they don't work at all, and there
 > is no other known devices on the market to check their assumption in
 > regard to this part of specs, and the spec does not describe how that
 > should work.
 >
 > Both of those downsides are due to the fact my understanding of DRM
 > subsystem is not that high. If another implementation would be proposed
 > by AMDGPU maintainers - I will gladly implement it here.
 >
 > v5->v6:
 >   * amdgpu: only apply dsc bpp to modes that match exactly the declared
 >     modes with this flag set.
 > v4->v5:
 >   * The patch was split into multiple
 >   * Disabled MSO parsing for eDP displays
 >   * Disabled MSO logs if not used
 >   * Minor codestyle changes: lines moved around, naming, passing of
 >     function arguments
 > v3->v4:
 >   * This patch now parses timings support flag on type VII block, instead
 >     of applying it unconditionally. Previously I didn't understand the
 >     spec properly.
 >   * Now it also is not being applied for non-supported and/or non-VII
 >     blocks in amdgpu driver.
 >
 > Regards,
 >
 > Lach
 >
 > Yaroslav Bolyukin (7):
 >    drm/edid: rename VESA block parsing functions to more generic name
 >    drm/edid: prepare for VESA vendor-specific data block extension
 >    drm/edid: MSO should only be used for non-eDP displays
 >    drm/edid: parse DSC DPP passthru support flag for mode VII timings
 >    drm/edid: for consistency, use mask everywhere for block rev parsing
 >    drm/edid: parse DRM VESA dsc bpp target
 >    drm/amd: use fixed dsc bits-per-pixel from edid
 >
 >   .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c |  16 +++
 >   drivers/gpu/drm/drm_displayid_internal.h      |  11 ++
 >   drivers/gpu/drm/drm_edid.c                    | 101 +++++++++++-------
 >   include/drm/drm_connector.h                   |   6 ++
 >   include/drm/drm_modes.h                       |  10 ++
 >   5 files changed, 107 insertions(+), 37 deletions(-)
 >