diff options
author | Oza Pawandeep <oza.oza@broadcom.com> | 2017-08-28 16:43:35 -0500 |
---|---|---|
committer | Bjorn Helgaas <bhelgaas@google.com> | 2017-09-05 12:27:03 -0500 |
commit | b91c26c6a539e26261cbe280b9f48311663ce655 (patch) | |
tree | e27ec47aabff5110f85dd1e894c66c6a5ea964d1 /README | |
parent | 39b7a4ff930143f17d05cd769ba2099f9249e898 (diff) | |
download | linux-b91c26c6a539e26261cbe280b9f48311663ce655.tar.bz2 |
PCI: iproc: Add 500ms delay during device shutdown
During soft reset (e.g., "reboot" from Linux) on some iProc-based SOCs, the
LCPLL clock and PERST both go off simultaneously. This seems in accordance
with the PCIe Card Electromechanical spec, r2.0, sec 2.2.3, which says the
clock goes inactive after PERST# goes active, but doesn't specify how long
the clock should be valid after PERST#.
However, we have observed that with the iProc Stingray, some Intel NVMe
endpoints, e.g., the P3700 400GB series, are not detected correctly upon
the next boot sequence unless the clock remains valid for some time after
PERST# is asserted.
Delay 500ms after asserting PERST# before performing a reboot. The 500ms
is experimentally determined.
Signed-off-by: Oza Pawandeep <oza.oza@broadcom.com>
[bhelgaas: changelog, add spec reference, fold in iproc_pcie_shutdown()
export from Arnd Bergmann <arnd@arndb.de>]
Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
Reviewed-by: Ray Jui <ray.jui@broadcom.com>
Reviewed-by: Scott Branden <scott.branden@broadcom.com>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions