aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/scsi/lpfc/lpfc_init.c
diff options
context:
space:
mode:
authorSuganath Prabu <suganath-prabu.subramani@broadcom.com>2019-07-30 03:43:57 -0400
committerMartin K. Petersen <martin.petersen@oracle.com>2019-07-30 12:46:06 -0400
commitdf9a606184bfdb5ae3ca9d226184e9489f5c24f7 (patch)
tree02a6dfc7230096d05565df8e7eea5dae557eae7a /drivers/scsi/lpfc/lpfc_init.c
parentscsi: hpsa: remove printing internal cdb on tag collision (diff)
downloadlinux-dev-df9a606184bfdb5ae3ca9d226184e9489f5c24f7.tar.xz
linux-dev-df9a606184bfdb5ae3ca9d226184e9489f5c24f7.zip
scsi: mpt3sas: Use 63-bit DMA addressing on SAS35 HBA
Although SAS3 & SAS3.5 IT HBA controllers support 64-bit DMA addressing, as per hardware design, if DMA-able range contains all 64-bits set (0xFFFFFFFF-FFFFFFFF) then it results in a firmware fault. E.g. SGE's start address is 0xFFFFFFFF-FFFF000 and data length is 0x1000 bytes. when HBA tries to DMA the data at 0xFFFFFFFF-FFFFFFFF location then HBA will fault the firmware. Driver will set 63-bit DMA mask to ensure the above address will not be used. Cc: <stable@vger.kernel.org> # 5.1.20+ Signed-off-by: Suganath Prabu <suganath-prabu.subramani@broadcom.com> Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions