Date: Wed, 08 Aug 2018 21:57:34 +0000 From: bugzilla-noreply@freebsd.org To: acpi@FreeBSD.org Subject: [Bug 230290] [patch] acpi: call sleep event handler when sleeping via command line Message-ID: <bug-230290-16045-iEmUwqJ93L@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230290-16045@https.bugs.freebsd.org/bugzilla/> References: <bug-230290-16045@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230290 --- Comment #13 from John Baldwin <jhb@FreeBSD.org> --- So my question is why does Linuxkpi care about the sleep state? Does it actually have conditional logic that it is using? If it really needs it, then what I think we should do is change DEVICE_SUSPEND/RESUME to add the type of suspend/resume being requested. This is somewhat complicated because devices can be suspended and resumed not as part of a system wide suspend and resume (e.g. 'devctl suspend foo0'), and for S0ix what you really want is to power down devices that aren't used even if the system isn't fully idle itself. So, the first question is why does Linuxkpi care what the system sleep state is vs what Dx state the GPU device is being placed in? -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230290-16045-iEmUwqJ93L>