Suspend routine runs in this order: 1. freeze processes 2. suspend drivers 3. turn off CPU
Resume routine is the opposite: 1. turn on CPU 2. resume drivers 3. wake up processes Sorting the actions differently would most probably cause system crash: - what would drivers do without the CPU? - How would userspace process access hardware without the drivers? So you can assume ueventd is woken up after your driver is resumed. Also you can verify that by turning on logs in ueventd, kernel/power/suspend.c<http://lxr.free-electrons.com/source/kernel/power/suspend.c>and adding no_console_suspend<https://groups.google.com/forum/#!msg/rowboat/MCkhcSGWZ2I/14ZKlKuWnjAJ>to your kernel command line. Emeric On Thu, May 9, 2013 at 10:18 AM, Durgadoss Ramanathan <[email protected] > wrote: > Hi, > > I have a driver that sends a UEvent [1] on its resume call back. > I want the 'ueventd' to catch this event, and act upon this. > > My doubt is whether ueventd be already running when my driver's resume > method is > being invoked . > > In other words, > when exactly does the ueventd start running once the android phone > 'resumes' from 'suspend' ? > > [1] kobject_uevent(&dev->kobj, KOBJ_ADD) > > -- > Regards > Durgadoss > > -- > -- > unsubscribe: [email protected] > website: http://groups.google.com/group/android-kernel > --- > You received this message because you are subscribed to the Google Groups > "Android Linux Kernel Development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel --- You received this message because you are subscribed to the Google Groups "Android Linux Kernel Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
