+Ville. On Wed, Nov 25, 2020 at 01:16:27PM +0530, Anshuman Gupta wrote: > On 2020-11-24 at 18:44:06 +0200, Imre Deak wrote: > > On Tue, Nov 24, 2020 at 03:28:47PM +0530, Anshuman Gupta wrote: > > > Platforms with South Display Engine on PCH, doesn't > > > require to get/put the AUX power domain in order to > > > access PPS register because PPS registers are always on > > > with South display on PCH. > > > > > > Cc: Imre Deak <imre.deak@xxxxxxxxx> > > > Cc: <stable@xxxxxxxxxxxxxxx> > > > Signed-off-by: Anshuman Gupta <anshuman.gupta@xxxxxxxxx> > > > > Could you describe the issue the patch is fixing? > > This fixes the display glitches causes by race between brightness > update thread and flip thread. Flips should work even with asynchronous DC3co (or any DC state) disabling, at least according to the spec the HW handles this. Only modesetting and AUX transfers have restriction wrt. DC state handling (where DC states need to get disabled). I think the exact restriction needs to be clarified with HW people: Is only the DC3co disable -> flip or also the opposite sequence problematic? Is it only DC3co or also DC5/6 affected? > While brightness is being updated it reads pp_ctrl reg to check > whether backlight is enabled and get/put the AUX power domain, this > enables and disable DC Off power well(DC3CO) back and forth. > > IMO there are two work item for above race needed to be addressed. > 1. Don't get AUX power for PPS register access (this patch addressed this). > 2. skl_program_plane() should wait for DC3CO exit delay to avoid any race with > DC3CO disable sequence. (WIP) DC states can be disabled asynchronously with a flip modeset, not only for panel brightness setting, but also AUX transfers for instance. So I think we'd need to add locking against DC state changes to intel_pipe_update_start()/end(). Probably the easiest would be to use the power_domains->lock for this. --Imre
