search for: nv50_disp_atomic_commit_core

...1 nv50_base_image_set [ 2368.141755] fb000000 [ 2368.141756] 0800 5 nv50_base_image_set [ 2368.141756] 00009400 [ 2368.141757] 00000000 [ 2368.141757] 04b00780 [ 2368.141757] 00100800 [ 2368.141758] 00001e00 [ 2368.141759] 0080 1 nv50_base_update [ 2368.141759] 00000001 [ 2368.141761] 0084 1 nv50_disp_atomic_commit_core [ 2368.141761] 80000000 [ 2368.141762] 0080 2 nv50_disp_atomic_commit_core [ 2368.141762] 00000002 [ 2368.141763] 00000000 Note that at no point does it call any of the nv50_head stuff. This is with just running 'modetest' pointed at the device. When I kill it, the screen turns off and...

...; + bool flushed = false; NV_ATOMIC(drm, "commit %d %d\n", atom->lock_core, atom->flush_disable); nv50_crc_atomic_stop_reporting(state); @@ -2003,6 +2004,8 @@ nv50_disp_atomic_commit_tail(struct drm_atomic_state *state) nv50_disp_atomic_commit_wndw(state, interlock); nv50_disp_atomic_commit_core(state, interlock); memset(interlock, 0x00, sizeof(interlock)); + + flushed = true; } } } @@ -2013,10 +2016,14 @@ nv50_disp_atomic_commit_tail(struct drm_atomic_state *state) nv50_disp_atomic_commit_wndw(state, interlock); nv50_disp_atomic_commit_core(state, interlock);...

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

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

Hi folks, Currently, when the device is removed (or the driver is unbound) the nouveau_drm structure de-allocated. However, it's still accessible from and used by some DRM layer callbacks. For example, file handles can be closed after the device has been removed (physically or otherwise). This series converts the Nouveau device structure to be allocated and de-allocated with the