Displaying 3 results from an estimated 3 matches for "caps_fetch".
Did you mean:
call_fetch
2018 Jul 19
0
[PATCH] kms/nv50: reject interlaced modes if the hardware doesn't support it
...e_new(struct nouveau_drm *, struct nv50_core **);
void nv50_core_del(struct nv50_core **);
@@ -17,6 +23,8 @@ struct nv50_core_func {
int (*ntfy_wait_done)(struct nouveau_bo *, u32 offset,
struct nvif_device *);
void (*update)(struct nv50_core *, u32 *interlock, bool ntfy);
+ bool (*caps_fetch)(struct nv50_disp *);
+ bool (*caps_parse)(struct nv50_disp *, struct nv50_core_caps *);
const struct nv50_head_func *head;
const struct nv50_outp_func {
@@ -32,6 +40,7 @@ void core507d_init(struct nv50_core *);
void core507d_ntfy_init(struct nouveau_bo *, u32);
int core507d_ntfy_wait_done(...
2018 Jul 20
7
[PATCH 0/6] improve feature detection
This is mainly for dropping interlaced modes on DP connectors if the GPU
would otherwise display garbage or EVO timesout.
It also adds experimental detection of the HDMI clock limit we currently
hard limit depending on the GPU generation.
Starting with GF110 GPUs, we can retrieve the limit directly from the GPU
and may make the hdmimhz parameter obsolete.
Testing this series with 2560x1440 or
2018 Aug 03
7
[PATCH v3 0/6] improve feature detection
small update to my last version I sent out.
Patches 3-6 are optional and should only improve detecting the max clocks
for HDMI and DP, but they didn't underwent big testing and I am a bit
concerned, that it might break detecting the DP limits on some boards.
Karol Herbst (6):
kms/nv50: move nv50_mstm out of the dp union in nouveau_encoder
kms/nv50: reject interlaced modes if the hardware