Niklas Cassel <Niklas.Cassel@xxxxxxx> writes: > The reason why many platforms do this override, is because: > "One of the requirement for modern x86 system to enter lowest power mode > (SLP_S0) is SATA IP block to be off. This is true even during when > platform is suspended to idle and not only in opportunistic (runtime) > suspend." > > "SATA IP block doesn't get turned off till SATA is in DEVSLP mode. Here > user has to either use scsi-host sysfs or tools like powertop to set > the sata-host link_power_management_policy to min_power." What? I'm confused. Here are several things that come to mind that when taken together with this statement confuse me. Perhaps I am wrong about one or more of them? 1) DEVSLP is an odd thing they invented to have ACPI twiggle a GPIO bit to cut the power rails to CDROM drives that aren't in active use. 2) SATA ALPM has the SATA controller automatically transition the sata link to lower power states when it isn't being used, and back again on use. 3) The SATA controller can not be suspended until all of its ports are suspended. 4) Suspending a SATA port does not happen during ALPM, but rather only either during system suspend, or when you enable runtime pm on the disk and the ata port in sysfs ( both are disabled by default ). A quick google led me to this: https://smarthdd.com/device_sleep.htm Which indicates that this DEVSLP thing is now being used to send an OOB signal to a SATA SSD so that it can power down its PHY completely, but isn't that what ATA SLEEP is for? aka. hdparm -Y. That command tells the drive that it can power down its PHY and then the host can power down its PHY and it takes a sata link reset to wake the drive back up. The link reset is easy to detect with minimum circuitry that is far simpler than the full sata PHY. It sounds like somebody decided to hack an OOB signal into ALPM rather than use ATA SLEEP, but why?
