Hi!
> Uses the machine_suspend trace point, called from the
> generic kernel suspend_enter function.
>
> Signed-off-by: Jean Pihet <[email protected]>
> CC: Thomas Renninger <[email protected]>
> ---
> kernel/power/suspend.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/kernel/power/suspend.c b/kernel/power/suspend.c
> index ecf7705..0650596 100644
> --- a/kernel/power/suspend.c
> +++ b/kernel/power/suspend.c
> @@ -22,6 +22,7 @@
> #include <linux/mm.h>
> #include <linux/slab.h>
> #include <linux/suspend.h>
> +#include <trace/events/power.h>
>
> #include "power.h"
>
> @@ -164,7 +165,9 @@ static int suspend_enter(suspend_state_t state)
> error = sysdev_suspend(PMSG_SUSPEND);
> if (!error) {
> if (!suspend_test(TEST_CORE) && pm_check_wakeup_events()) {
> + trace_machine_suspend(state);
> error = suspend_ops->enter(state);
> + trace_machine_suspend(PWR_EVENT_EXIT);
> events_check_enabled = false;
> }
> sysdev_resume();
Ok... why this place? I mean, perhaps suspend time should include
device suspend?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
