| commit | 76a5af841755a0427229a6a77ca83781d61e5b2a | |
| author | Kai-Heng Feng <kai.heng.feng@canonical.com> | |
| Mon, 26 Jun 2017 20:39:54 +0000 (26 16:39 -0400) | ||
| committer | Jens Axboe <axboe@kernel.dk> | |
| Wed, 28 Jun 2017 14:14:13 +0000 (28 08:14 -0600) | ||
| tree | d7593e41bbe6f81829faf3ac1e35c97b16c8bc20 | treesnapshot (tar.gz zip) |
| parent | 7aa1f42752f0d31a5bb6d0d5bac92fc8c2044ce2 | commitdiff |
nvme: explicitly disable APST on quirked devices
A user reports APST is enabled, even when the NVMe is quirked or with
option "default_ps_max_latency_us=0".
The current logic will not set APST if the device is quirked. But the
NVMe in question will enable APST automatically.
Separate the logic "apst is supported" and "to enable apst", so we can
use the latter one to explicitly disable APST at initialiaztion.
BugLink: https://bugs.launchpad.net/bugs/1699004
Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
Reviewed-by: Andy Lutomirski <luto@kernel.org>
Signed-off-by: Keith Busch <keith.busch@intel.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
A user reports APST is enabled, even when the NVMe is quirked or with
option "default_ps_max_latency_us=0".
The current logic will not set APST if the device is quirked. But the
NVMe in question will enable APST automatically.
Separate the logic "apst is supported" and "to enable apst", so we can
use the latter one to explicitly disable APST at initialiaztion.
BugLink: https://bugs.launchpad.net/bugs/1699004
Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
Reviewed-by: Andy Lutomirski <luto@kernel.org>
Signed-off-by: Keith Busch <keith.busch@intel.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
| drivers/nvme/host/core.c | diffblobblamehistory | |
| drivers/nvme/host/nvme.h | diffblobblamehistory |