nvme: honor CRTO for the controller ready timeout

[seuros]

Summary

CAP.TO is a 8b field and saturate at 127.5 seconds; a controller
that needs longer reports the real worst case in CRTO.CRWMT.
Waiting only CAP.TO can reset a controller that is still within its declared
recovery time after e.g. an abrupt shutdown.
Taking the larger of CRTO.CRWMT and CAP.TO when CAP.CRWMS show CRTO support.

[ngie]

@seuros : I won't be able to provide a ship-it this weekend, but could you please provide the spec link for this and other related items in the future so @adrian and I can help provide you quicker ship-its?

(to be fair I have the attention span of Doug from Up and the short-term memory of a Dory from Finding Nemo: having the info helps future me track down what I was thinking if I need to look it up later :)..)

[seuros]

In D59631#1377509, @ngie wrote:

@seuros : I won't be able to provide a ship-it this weekend, but could you please provide the spec link for this and other related items in the future so @adrian and I can help provide you quicker ship-its?

(to be fair I have the attention span of Doug from Up and the short-term memory of a Dory from Finding Nemo: having the info helps future me track down what I was thinking if I need to look it up later :)..)

CAP.TO Figure 36, p.57
CRTO Figure 57, offset 68h, page 73

Everything is in NVM-Express-Base-Specification-Revision-2.4-Ratified-2026.07.31.pdf .

The new diffs have references.