drm/mali-dp: Fix malidp_atomic_commit_hw_done() for event sending.
Mali DP hardware has a 'go' bit (config_valid) for making the new scene parameters active at the next page flip. The problem with the current code is that the driver first sets this bit and then proceeds to wait for confirmation from the hardware that the configuration has been updated before arming the vblank event. As config_valid is actually asserted by the hardware after the vblank event, during the prefetch phase, when we get to arming the vblank event we are going to send it at the next vblank, in effect halving the vblank rate from the userspace perspective. Fix it by sending the userspace event from the IRQ handler, when we handle the config_valid interrupt, which syncs with the time when the hardware is active with the new parameters. Reported-by: Alexandru-Cosmin Gheorghe <alexandru-cosmin.gheorghe@arm.com> Signed-off-by: Liviu Dudau <liviu.dudau@arm.com>
This commit is contained in:
@@ -22,6 +22,7 @@ struct malidp_drm {
|
||||
struct malidp_hw_device *dev;
|
||||
struct drm_crtc crtc;
|
||||
wait_queue_head_t wq;
|
||||
struct drm_pending_vblank_event *event;
|
||||
atomic_t config_valid;
|
||||
u32 core_id;
|
||||
};
|
||||
|
Reference in New Issue
Block a user