Change Details

Add `enum sleep_type stype` parameter in `power_suspend/resume` event handlers, as with the introduction of s2idle there are more than one type of suspend. When going to s2idle, set Linux' `pm_suspend_target_state` to `PM_SUSPEND_TO_IDLE` instead of `PM_SUSPEND_MEM` (for S3) in all cases. This is necessary because more recent versions of the amdgpu DRM drivers have different paths for when entering s2idle & S0ix is supported than S3.

Add `enum sleep_type stype` parameter in `power_suspend/resume` event handlers, as with the introduction of s2idle there are more than one type of suspend. When going to s2idle, set Linux' `pm_suspend_target_state` to `PM_SUSPEND_TO_IDLE` instead of `PM_SUSPEND_MEM` (for S3) in all cases. This is necessary because more recent versions of the amdgpu DRM drivers have different paths for when entering s2idle & S0ix is supported than S3. Not sure if passing this in the eventhandler is the best approach; maybe we'd want a global similar to `pm_suspend_target_state` on Linux. This would make it easier for other device drivers (e.g. Nvidia driver) to go down different paths in S0ix vs S3 without having to register an eventhandler.

Add `enum sleep_type stype` parameter in `power_suspend/resume` event handlers, as with the introduction of s2idle there are more than one type of suspend. When going to s2idle, set Linux' `pm_suspend_target_state` to `PM_SUSPEND_TO_IDLE` instead of `PM_SUSPEND_MEM` (for S3) in all cases. This is necessary because more recent versions of the amdgpu DRM drivers have different paths for when entering s2idle & S0ix is supported than S3. Not sure if passing this in the eventhandler is the best approach; maybe we'd want a global similar to `pm_suspend_target_state` on Linux. This would make it easier for other device drivers (e.g. Nvidia driver) to go down different paths in S0ix vs S3 without having to register an eventhandler.