search for: lvdsconf

...c index 9a6e2cb..d3595b2 100644 --- a/drivers/gpu/drm/nouveau/nouveau_connector.c +++ b/drivers/gpu/drm/nouveau/nouveau_connector.c @@ -355,7 +355,7 @@ nouveau_connector_detect_lvds(struct drm_connector *connector, bool force) * valid - it's not (rh#613284) */ if (nv_encoder->dcb->lvdsconf.use_acpi_for_edid) { - if (!(nv_connector->edid = nouveau_acpi_edid(dev, connector))) { + if ((nv_connector->edid = nouveau_acpi_edid(dev, connector))) { status = connector_status_connected; goto out; }

...pclk >= 165000) >> + if (pclk >= 165000 && outp->info.duallink_possible) >> *conf |= 0x0100; > I think it might be more robust to key this off the SOR protocol, rather > than duplicating the condition above. You mean disp->sor.lvdsconf? What do I do with that? Or did you have something else in mind? > >> break; >> case DCB_OUTPUT_LVDS: >> diff --git a/drm/nouveau/nvkm/engine/disp/nv50.c b/drm/nouveau/nvkm/engine/disp/nv50.c >> index 32e73a9..ceecd0e 100644 >> --- a/drm/nouveau...

...data = *(u32 *)args; + if (type && !dcb_outp_match(bios, type, mask, &ver, &hdr, &outp)) + return -ENODEV; switch (mthd & ~0x3f) { case NV50_DISP_SOR_PWR: @@ -71,6 +79,10 @@ nv50_sor_mthd(struct nouveau_object *object, u32 mthd, void *args, u32 size) priv->sor.lvdsconf = data & NV50_DISP_SOR_LVDS_SCRIPT_ID; ret = 0; break; + case NV94_DISP_SOR_DP_TRAIN: + ret = nouveau_dp_train(&priv->base, priv->sor.dp, &outp, + head, data); + break; default: BUG_ON(1); } diff --git a/drivers/gpu/drm/nouveau/core/include/core/class.h b/...

...amp;hdr, &outp)) >> + return -ENODEV; >> >> switch (mthd & ~0x3f) { >> case NV50_DISP_SOR_PWR: >> @@ -71,6 +79,10 @@ nv50_sor_mthd(struct nouveau_object *object, u32 mthd, void *args, u32 size) >> priv->sor.lvdsconf = data & NV50_DISP_SOR_LVDS_SCRIPT_ID; >> ret = 0; >> break; >> + case NV94_DISP_SOR_DP_TRAIN: >> + ret = nouveau_dp_train(&priv->base, priv->sor.dp, &outp, >> +...

https://bugs.freedesktop.org/show_bug.cgi?id=55412 Priority: medium Bug ID: 55412 Assignee: nouveau at lists.freedesktop.org Summary: Screen turns black during boot after driver tries to set mode on NV50 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux

...type, mask, &ver, &hdr, &outp)) > + return -ENODEV; > > switch (mthd & ~0x3f) { > case NV50_DISP_SOR_PWR: > @@ -71,6 +79,10 @@ nv50_sor_mthd(struct nouveau_object *object, u32 mthd, void *args, u32 size) > priv->sor.lvdsconf = data & NV50_DISP_SOR_LVDS_SCRIPT_ID; > ret = 0; > break; > + case NV94_DISP_SOR_DP_TRAIN: > + ret = nouveau_dp_train(&priv->base, priv->sor.dp, &outp, > + head, data); > +...

From: Hauke Mehrtens <hauke at hauke-m.de> Without this patch a pixel clock rate above 165 MHz on a TMDS link is assumed to be dual link. This is true for DVI, but not for HDMI. HDMI supports no dual link, but it supports pixel clock rates above 165 MHz. Only activate Dual Link mode when it is actual possible. Signed-off-by: Hauke Mehrtens <hauke at hauke-m.de> Signed-off-by: Ilia

It seems it was only locking up in the context of nouveau_hw_save_vga_fonts, when it actually did something (because the console wasn't already in graphics mode). Signed-off-by: Francisco Jerez <currojerez at riseup.net> --- drivers/gpu/drm/nouveau/nouveau_hw.c | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_hw.c

This patch series adds TV-out modesetting support to the KMS implementation. I've tried to test it on all the hardware I've got at hand (that is nv11, nv17, nv34, nv35, nv40, nv4b) with every possible output combination; I believe it has reached a mergeable state, however it depends on some commits from drm-next that haven't got into Linus' tree yet, if you agree to merge this

Most of the reason I'm asking for an RFC here is because this code pulls a lot of code out of i915 and into shared DP helpers. Anyway-nouveau's HPD related code has been collecting dust for a while. Other then the occasional runtime PM related and MST related fixes, we're missing a lot of nice things that have been added to DRM since this was originally written. Additionally, the code

To start off: this patch series is less work to review then it looks - most (but not all) of the nouveau related work has already been reviewed elsewhere. Most of the reason I'm asking for an RFC here is because this code pulls a lot of code out of i915 and into shared DP helpers. Anyway-nouveau's HPD related code has been collecting dust for a while. Other then the occasional runtime PM

Most of the reason I'm asking for an RFC here is because this code pulls a lot of code out of i915 and into shared DP helpers. Anyway-nouveau's HPD related code has been collecting dust for a while. Other then the occasional runtime PM related and MST related fixes, we're missing a lot of nice things that have been added to DRM since this was originally written. Additionally, the code

To start off: this patch series is less work to review then it looks - most (but not all) of the nouveau related work has already been reviewed elsewhere. Most of the reason I'm asking for an RFC here is because this code pulls a lot of code out of i915 and into shared DP helpers. Anyway-nouveau's HPD related code has been collecting dust for a while. Other then the occasional runtime PM