search for: duallink_possible

...ode, switch (nv_encoder->dcb->type) { case DCB_OUTPUT_TMDS: if (nv_encoder->dcb->sorconf.link & 1) { - if (mode->clock < 165000) - proto = 0x1; - else - proto = 0x5; + proto = 0x1; + if (mode->clock >= 165000 && + nv_encoder->dcb->duallink_possible) + proto |= 0x4; } else { proto = 0x2; } diff --git a/drm/nouveau/nvkm/engine/disp/gf119.c b/drm/nouveau/nvkm/engine/disp/gf119.c index 186fd3a..8691b68 100644 --- a/drm/nouveau/nvkm/engine/disp/gf119.c +++ b/drm/nouveau/nvkm/engine/disp/gf119.c @@ -158,7 +158,7 @@ exec_clkcmp(struct n...

...proto = 0x1; >> - else >> - proto = 0x5; >> + proto = 0x1; >> + if (mode->clock >= 165000 && >> + nv_encoder->dcb->duallink_possible) >> + proto |= 0x4; > This is a somewhat flaky condition, given that one could plug a > single-link HDMI monitor into a duallink-capable TMDS connector. > > Still, it's an improvement :) Yeah, FWIW I thought of that (for the second patch too). All...

...hdmi_enable(encoder, nv_crtc, nv_connector, state, mode, hda); if (nv_encoder->outp.or.link & 1) { @@ -1786,7 +1786,7 @@ nv50_sor_atomic_enable(struct drm_encoder *encoder, struct drm_atomic_state *sta */ if (mode->clock >= 165000 && nv_encoder->dcb->duallink_possible && - !drm_detect_hdmi_monitor(nv_connector->edid)) + !nv_connector->base.display_info.is_hdmi) proto = NV507D_SOR_SET_CONTROL_PROTOCOL_DUAL_TMDS; } else { proto = NV507D_SOR_SET_CONTROL_PROTOCOL_SINGLE_TMDS_B; diff --git a/drivers/gpu/drm/nouveau/dispnv50/head....

...> case DCB_OUTPUT_TMDS: > if (nv_encoder->dcb->sorconf.link & 1) { > - if (mode->clock < 165000) > - proto = 0x1; > - else > - proto = 0x5; > + proto = 0x1; > + if (mode->clock >= 165000 && > + nv_encoder->dcb->duallink_possible) > + proto |= 0x4; This is a somewhat flaky condition, given that one could plug a single-link HDMI monitor into a duallink-capable TMDS connector. Still, it's an improvement :) > } else { > proto = 0x2; > } > diff --git a/drm/nouveau/nvkm/engine/disp/gf119.c b/drm...

...er->outp.or.link & 1) { > @@ -1786,7 +1786,7 @@ nv50_sor_atomic_enable(struct drm_encoder *encoder, struct drm_atomic_state *sta > */ > if (mode->clock >= 165000 && > nv_encoder->dcb->duallink_possible && > - !drm_detect_hdmi_monitor(nv_connector->edid)) > + !nv_connector->base.display_info.is_hdmi) > proto = NV507D_SOR_SET_CONTROL_PROTOCOL_DUAL_TMDS; > } else { >...

...proto = 0x5; + proto = 0x1; + /* Only enable dual-link if: + * - Need to (i.e. rate > 165MHz) + * - DCB says we can + * - Not an HDMI monitor, since there's no dual-link + * on HDMI. + */ + if (mode->clock >= 165000 && + nv_encoder->dcb->duallink_possible && + !drm_detect_hdmi_monitor(nv_connector->edid)) + proto |= 0x4; } else { proto = 0x2; } diff --git a/drm/nouveau/nvkm/engine/disp/gf119.c b/drm/nouveau/nvkm/engine/disp/gf119.c index 186fd3a..f031466 100644 --- a/drm/nouveau/nvkm/engine/disp/gf119.c +++ b/drm/nouvea...

...i.e. rate > 165MHz) + * - Not an HDMI monitor, since there's no dual-link + * on HDMI. Of course in order to determine that, + * we need the EDID. So if no EDID, just let it + * slide. + */ + if (mode->clock >= 165000 && + nv_encoder->dcb->duallink_possible && + (!nv_connector->edid || + !drm_detect_hdmi_monitor(nv_connector->edid))) + proto |= 0x4; } else { proto = 0x2; } diff --git a/drm/nouveau/nvkm/engine/disp/gf119.c b/drm/nouveau/nvkm/engine/disp/gf119.c index 186fd3a..f031466 100644 --- a/drm/nouveau/nvkm...

These patches are adding support for outputting 2560x1440 at 56 over HDMI. This needs a pixel clock of 225 MHz which was not supported before. This was tested in a dual monitor setup with a GF114 (GTX 560 TI) and one HDMI monitor running with 2560x1440 at 56 and one DVI monitor running with 1920x1200 at 60. This still needs testing on other graphics cards and with dual link DVI. There is no

These patches are adding support for outputting 2560x1440 at 56 over HDMI. This needs a pixel clock of 225 MHz which was not supported before. This was tested in a dual monitor setup with a GF114 (GTX 560 TI) and one HDMI monitor running with 2560x1440 at 56 and one DVI monitor running with 1920x1200 at 60. This still needs testing on other graphics cards and with dual link DVI. There is no

THIS IS UNTESTED for anything other than i915. Use previously parsed EDID where possible for display audio/hdmi detection. This in turn reduces edid_blob_ptr usage in a number of places. Further reduce edid_blob_ptr usage, and document that it should not be used by drivers directly. BR, Jani. Cc: Alain Volmat <alain.volmat at foss.st.com> Cc: Alex Deucher <alexander.deucher at

This is the beginnings of HDMI 2.0 support. All of the "extra" features are left out, such as 12/16bpc, YUV420, etc. I've verified that with this code, a GP108 (GT1030) can switch between 4k at 60 and 1920x1080 at 60 on a LG 4K TV. Further, I've verified via i2c tools, that the SCDC writes really do happen. I suspect that the patch for keeping track of the high-speed TMDS

https://bugs.freedesktop.org/show_bug.cgi?id=40747 Summary: The new nouveau kernel module fails to use my monitor's native resolution Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: