-- Daniel >> I guess I don't really understand your description, but it does sound >> strange ... runtime pm enabling from my patch is only about D3, power >> well changes are still done. And as long as we have anything enabled >> (even with PSR) we'll prevent D3. >> >> So the only thing I can think of is that somehow D3 wreaks something >> in the PSR setup and that's causing issues. Unfortunately I have no >> idea about our hw details around PSR and D3, so no idea. Maybe Art has >> some? > -- Rodrigo >I don't know this relation as well. When I found this LPSP maks that >made PSR working it was totally by forcing all masks and start >removing one by one up to the point that this Low Power something did >the trick. At that time Artur had told about power well handling >enabled, but now after Mathew reported that issue I noticed this Low >power flag was also related to runtime PM... > Let me see if I understand what is happening. Runtime PM seemed to cause PSR to miss some screen updates when you had LPSP masked, then you stopped masking LPSP and it fixed the missing updates? My first guess is that you are not in LPSP at this point, so removing the mask is effectively disabling PSR, which prevents PSR from missing screen updates. Are you still getting good PSR residency with LPSP masked in this situation? The LPSP mask is only there fro debug. We don't normally want PSR to enter without LPSP because there can be undesirable things like clocks stopping which could break the display audio controller and codec. _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
