Dominik Brodowski wrote:
Hi,
Also, the actual checking for bm_activity should be common code, e.g.
It's policy specific. Each policy could have its own method to calculate
bm_activity.
What to do once bm_activity is or was detected, yes. How to determine
whether there is current bus mastering activity, no -- that's core stuff,
not policy stuff.
I had the experience that tweaking how bm_activity is detected could help a lot.
An aggressive policy might also accept some faulty transitions in respect of
more
power saving achievements.
What about the way in the middle?:
A general check_bm_activity() function. This one can be overridden by more
complex policy drivers/modules.
I hope to get some time the next days to play with all this...
Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
