summaryrefslogtreecommitdiff
path: root/drivers/accessibility
diff options
context:
space:
mode:
authorKevin Barnett <kevin.barnett@microchip.com>2022-02-02 00:48:53 +0300
committerMartin K. Petersen <martin.petersen@oracle.com>2022-02-08 07:38:35 +0300
commit00598b056aa6d46c7a6819efa850ec9d0d690d76 (patch)
tree2ad3d6a39d6db2efdc4c0f4edb90f36920c69e8d /drivers/accessibility
parent5d8fbce04d36dfd837d655e3d1b66e44b8fafbe5 (diff)
downloadlinux-00598b056aa6d46c7a6819efa850ec9d0d690d76.tar.xz
scsi: smartpqi: Expose SAS address for SATA drives
Remove UNIQUE_WWID_IN_REPORT_PHYS_LUN PQI feature. This feature was originally added to solve a problem with NVMe drives, but this problem has since been solved a different way, so this PQI feature is no longer required for any type of drive. The kernel was not creating symbolic links in sysfs between SATA drives and their enclosure. The driver was enabling the UNIQUE_WWID_IN_REPORT_PHYS_LUN PQI feature, which causes the FW to return a WWID for SATA drives that is derived from a unique ID read from the SATA drive itself. The driver was exposing this WWID as the drive's SAS address. However, because this SAS address does not match the SAS address returned by an enclosure's SES Page 0xA data, the Linux kernel was not able to match a SATA drive with its enclosure. Link: https://lore.kernel.org/r/164375213346.440833.12379222470149882747.stgit@brunhilda.pdev.net Reviewed-by: Mike McGowen <mike.mcgowen@microchip.com> Reviewed-by: Scott Benesh <scott.benesh@microchip.com> Reviewed-by: Scott Teel <scott.teel@microchip.com> Signed-off-by: Kevin Barnett <kevin.barnett@microchip.com> Signed-off-by: Don Brace <don.brace@microchip.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'drivers/accessibility')
0 files changed, 0 insertions, 0 deletions