On Sun, Oct 14, 2018 at 5:01 AM Michael Mrozek EvilDragon@openpandora.org wrote:
On Sat, 2018-10-13 at 19:29 +0300, Grazvydas Ignotas wrote:
Hi,
Okay, I now measured the power consumption and compared a 4GB unit with Self-Refresh disabled, the same unit with Self-Refresh enabled and a 2GB RAM unit (old mainboard and old CPU board). And... well, either Idle / Self-Refresh is not working properly or there isn't really a difference yet.
How are you disabling self-refresh? Note that my patches aren't disabling it yet, I just asked if we should do it.
Ah, okay! I thought that was in aTc's latest U-Boot. So it's only DLL disabled then, okay!
No, there is no workaround there, it should still hang. The patches fix other mistakes, but not the actual issue.
So you want a workaround patch there? Should we disable self-refresh or DLL then?
You also have to blank the screen, otherwise DSS is constantly reading the framebuffer (which sits in RAM) to display it.
Hm, there's one thing I understand then:
If our issue is self-refresh and that will only happen if nothing is on the screen, why does the unit freeze in our tests? Because I always have something showing on the screen, I never blank it.
I never said it only happens with blanking screen.
What I meant to say is that measuring power consumption with screen on probably makes little sense because of DSS reading RAM. Only during vsync/vblank (and maybe hblank too) it will be entering self-refresh, instead of anytime with the screen off, so you'd see little power usage difference. And because you work with video a lot, I wrongly (?) assumed you'd have vsync in mind while reading this.
GraÅžvydas