Skip to contentSkip to conversation

Suspend to RAm query

DISCUSSION deepaksi 2 participants 3 messages Jun 28, 2011 – Jul 3, 2011

lore
Share & tools
lore

deepaksi

author
#0 lore raw

Hi All,

I have a very basic query w.r.t the place to handle the standby/suspend process for the devices in the system.

Should it be done at the driver level or in the machine/platform specific code ?

There are instances where I need some specific functionality in the standby mode, or some extra functionality
in the suspend mode at the device level. Is that the reason for differentiating between the suspend and standby at
the platform code level, because in platform code we get different states signifying a suspend or a standby ?

Thanks
Deepak

#1 lore raw

Hi,

Quoted 8 lines · deepaksi

Hi All,

I have a very basic query w.r.t the place to handle the standby/suspend process for the devices in the system.

Should it be done at the driver level or in the machine/platform specific code ?

Quoted 6 lines

There are instances where I need some specific functionality in the standby mode, or some extra functionality
in the suspend mode at the device level. Is that the reason for differentiating between the suspend and standby at
the platform code level, because in platform code we get different states signifying a suspend or a standby ?

Yes, it is.

The platform suspend callbacks in strcut platform_suspend_ops (as defined in include/linux/suspend.h) take a suspend_state_t argument indicating what state is being requested. You can get the information from there, if I understood your problem description correctly.

Thanks,
Rafael

#2 lore raw
In reply to deepaksi

Hi,

Quoted 8 lines · deepaksi

Hi All,

I have a very basic query w.r.t the place to handle the standby/suspend process for the devices in the system.

Should it be done at the driver level or in the machine/platform specific code ?

Quoted 6 lines

There are instances where I need some specific functionality in the standby mode, or some extra functionality
in the suspend mode at the device level. Is that the reason for differentiating between the suspend and standby at
the platform code level, because in platform code we get different states signifying a suspend or a standby ?

Yes, it is.

The platform suspend callbacks in strcut platform_suspend_ops (as defined in include/linux/suspend.h) take a suspend_state_t argument indicating what state is being requested. You can get the information from there, if I understood your problem description correctly.

Thanks,
Rafael