aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/scsi/libsas/sas_init.c
diff options
context:
space:
mode:
authorJohn Garry <[email protected]>2019-04-12 08:57:56 +0000
committerMartin K. Petersen <[email protected]>2019-04-15 22:55:01 +0000
commitd8649fc1c5e40e691d589ed825998c36a947491c (patch)
treeb0cbf9932a4cb53546694e63a02afb858bfb5b5d /drivers/scsi/libsas/sas_init.c
parentscsi: libsas: Inject revalidate event for root port event (diff)
downloadkernel-d8649fc1c5e40e691d589ed825998c36a947491c.tar.gz
kernel-d8649fc1c5e40e691d589ed825998c36a947491c.zip
scsi: libsas: Do discovery on empty PHY to update PHY info
When we discover the PHY is empty in sas_rediscover_dev(), the PHY information (like negotiated linkrate) is not updated. As such, for a user examining sysfs for that PHY, they would see incorrect values: root@(none)$ cd /sys/class/sas_phy/phy-0:0:20 root@(none)$ more negotiated_linkrate 3.0 Gbit root@(none)$ echo 0 > enable root@(none)$ more negotiated_linkrate 3.0 Gbit So fix this, simply discover the PHY again, even though we know it's empty; in the above example, this gives us: root@(none)$ more negotiated_linkrate Phy disabled We must do this after unregistering the device associated with the PHY (in sas_unregister_devs_sas_addr()). Signed-off-by: John Garry <[email protected]> Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'drivers/scsi/libsas/sas_init.c')
0 files changed, 0 insertions, 0 deletions