summaryrefslogtreecommitdiff
path: root/board/Marvell/mvebu_armada-37xx
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2017-08-03 02:31:02 -0700
committerTom Rini <trini@konsulko.com>2017-08-13 15:17:33 -0400
commitbeb5f521392e7da208455f3bf0c86bc141c0879d (patch)
tree23ea2f79212bfd284430336e34b2992835d5001f /board/Marvell/mvebu_armada-37xx
parentf81d83d53454a108f0317c1debd8af7edc8413be (diff)
nvme: Handle zero Maximum Data Transfer Size (MDTS)
Maximum Data Transfer Size (MDTS) field indicates the maximum data transfer size between the host and the controller. The host should not submit a command that exceeds this transfer size. The value is in units of the minimum memory page size and is reported as a power of two (2^n). The spec also says: a value of 0h indicates no restrictions on transfer size. On the real NVMe card this is normally not 0 due to hardware restrictions, but with QEMU emulated NVMe device it reports as 0. In nvme_blk_read/write() below we have the following algorithm for maximum number of logic blocks per transfer: u16 lbas = 1 << (dev->max_transfer_shift - ns->lba_shift); dev->max_transfer_shift being 0 will for sure cause lbas to overflow. Let's use 20. With this fix, the NVMe driver works on QEMU emulated NVMe device. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Tom Rini <trini@konsulko.com>
Diffstat (limited to 'board/Marvell/mvebu_armada-37xx')
0 files changed, 0 insertions, 0 deletions