Skip to contentSkip to conversation

API for querying the resume cause [2]

DISCUSSION Yan Pashkovsky 2 participants 2 messages Nov 3, 2015

lore
Share & tools
lore
#0 lore raw

Hi everyone!

I was writing you on 21 of August (http://marc.info/?t=144007145600001&r=1&w=2) about API for querying the resume cause. I was looking at the releases of linux kernel and discovered this:

"Finally, the PM core gets a new mechanism that can be used by device drivers to distinguish between suspend-to-RAM (based on platform firmware support) and suspend-to-idle (or other variants of system suspend the platform firmware is not involved in) and possibly optimize their device suspend/resume handling accordingly"

        http://lkml.iu.edu/hypermail/linux/kernel/1511.0/01164.html

Is it what we were discussing? If yes - that's fine, I'll contact systemd team. If no - is this API exists in someone's todo list or smth like this? Are there any plans for this?

Kind regards,
Yan

#1 lore raw

Hi,

Quoted 12 lines · Yan Pashkovsky

Hi everyone!

I was writing you on 21 of August
(http://marc.info/?t=144007145600001&r=1&w=2) about API for querying the resume cause. I was looking at the releases of linux kernel and discovered this:

"Finally, the PM core gets a new mechanism that can be used by device drivers to distinguish between suspend-to-RAM (based on platform firmware support) and suspend-to-idle (or other variants of system suspend the platform firmware is not involved in) and possibly optimize their device suspend/resume handling accordingly"

Quoted 5 lines
        http://lkml.iu.edu/hypermail/linux/kernel/1511.0/01164.html

Is it what we were discussing? If yes - that's fine, I'll contact systemd team. If no - is this API exists in someone's todo list or smth like this? Are there any plans for this?

This is (a small) part of an API that may be used for this purpose (and is there in someone's to-do list), but it's targeted at debugging.

Thanks,
Rafael