Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support setting HDMI/DP content types #1035

Open
Xyene opened this issue Oct 10, 2022 · 1 comment
Open

Support setting HDMI/DP content types #1035

Xyene opened this issue Oct 10, 2022 · 1 comment

Comments

@Xyene
Copy link
Contributor

Xyene commented Oct 10, 2022

Newer versions of the HDMI and DP specs support specifying a "content type" for the media being presented, one of

  • Not defined
  • Graphics
  • Photo
  • Video
  • Game

Some monitors will switch display profiles based on these modes. For instance, they may reduce latency in "Game" mode, be more careful with frame timing for "Video", color accuracy in "Graphics", saturation in "Photo", etc.

Wayland allows us to specify the mode of our content through the new content-type-v1 protocol (protocol, discussion, example implementation in mpv). It is up to the compositor to then do something with the mode (e.g., it may only be able to do something if our surface is fullscreen).

For LG's purposes, "Game" is probably the right choice.

If we wanted to be fancy, we could ferry the mode set on the Windows side to the Linux host. I've tried to figure out what Windows calls this through Googles for "DP VSC SDP Content Type", "HDMI InfoFrame", "HDMI Content Type", etc., to no avail, but it must exist because Windows implements this too.

@gnif
Copy link
Owner

gnif commented Oct 10, 2022

Agreed that "Game" is the right choice here.

@quantum5 quantum5 assigned quantum5 and unassigned quantum5 Oct 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants