29 Jan
2010
29 Jan
'10
11:17 a.m.
On Fri, Jan 29, 2010 at 09:01:30AM +0200, Peter Ujfalusi wrote:
What I have found out is that after boot these bits were set (obviously), after the audio activity, they were cleared (not all, since if the given DAPM control was not in the path, it was left enabled either way). Now these bits are 0 after boot, and only enabled, when a certain path needs it. In short: the overall power consumption was higher after boot, than what was after for example the playback was stopped...
Hrm, that shouldn't happen - DAPM should be syncing during startup which will turn off anything that's left turned on. I'll have to fake up a test for this, I'd not notice problems normally since all the devices I start with power everything off by default.