On Fri, Oct 12, 2018 at 6:36 PM Michael Mrozek EvilDragon@openpandora.org wrote:
Well, hardware- or softwarewise broken?
Probably hardware, there is very little software control for how it does it's thing (see below).
If I understood correctly, then Self-Refresh is being entered and exited by the kernel. So both the call and the procedure is being controlled by software.
Not on OMAP5's EMIF, here it's all done by EMIF hardware. You can only control the on/off switch for the feature, time how long it has to idle (no RAM access by anything) before it starts the procedure and some limited timing parameters.
But our chip also supports the (optional) feature "Auto Self-Refresh".
How do you know that? It's not mentioned in feature list of our RAM's datasheet.
So - are we talking about AUTO self-refresh or self-refresh which causes our issue?
The "manual" one, which is handled by OMAP5 hardware.
Since Auto Self-Refresh is optional, maybe it's disabled in our setup?
Yes
If Auto Self-Refresh does the same as Self-Refresh (but it's being handled by the RAM itself), maybe that woukd work instead?
Yes there is a bit for that in OMAP5, might try it later.
GraÅžvydas