search for: core_notifier_3_cap

Displaying 2 results from an estimated 2 matches for "core_notifier_3_cap".

2018 Aug 03
2
[PATCH v3 5/6] kms/nv50: detect HDMI max MHz correctly
On Fri, Aug 3, 2018 at 8:19 AM, Karol Herbst <kherbst at redhat.com> wrote: > v2: clean up left over comments > don't overwrite hdmimhz parameter > cap to 297MHz > > Signed-off-by: Karol Herbst <kherbst at redhat.com> > --- > drm/nouveau/dispnv50/disp.c | 5 +++++ > drm/nouveau/nouveau_connector.c | 15 ++++++++++----- >
2018 Aug 03
0
[PATCH v3 5/6] kms/nv50: detect HDMI max MHz correctly
...ome ideas where we could use them or fix potential issues we don't know yet how to fix them?): SINGLE_LVDS18 SINGLE_LVDS24 DUAL_LVDS18 DUAL_LVDS24 SINGLE_TMDS_A SINGLE_TMDS_B DUAL_TMDS DP_A DP_B besides that there is tons of stuff inside open-gpu-doc/Display-Class-Methods/2/cl907d.h, it is the CORE_NOTIFIER_3_CAPABILITIES stuff. >> + >> if (hdmi) { >> - if (nouveau_hdmimhz > 0) >> - return nouveau_hdmimhz * 1000; >> - /* Note: these limits are conservative, some Fermi's >> - * can do 297 MHz....