summaryrefslogtreecommitdiff
path: root/drivers/net/tsi108_eth.c
diff options
context:
space:
mode:
authorKashyap, Desai <kashyap.desai@lsi.com>2010-06-17 13:11:48 +0400
committerJames Bottomley <James.Bottomley@suse.de>2010-07-27 21:02:35 +0400
commitcc7e9f5f9999d9c015686ab4a622e1fb529391eb (patch)
tree55bde51c2d1687a57b9bac9608961c33e9db20b3 /drivers/net/tsi108_eth.c
parentb68bf096d4211bb6490955f86842d8291e8ae218 (diff)
downloadlinux-cc7e9f5f9999d9c015686ab4a622e1fb529391eb.tar.xz
[SCSI] mptfusion: Added code for occationally SATA hotplug failure.
Issue: SATA hotplug does not work sometimes. At the time of ADD device/ADD phys disk, drive may fail to add SATA device due to temporary SAS Address for SATA device generated by firmware. Final SAS address for SATA driver will be generated only after disk spinup is done. This may take some times for slow spining SATA drives. At phy link up driver gets attached device sas address and stores into phyinfo. At the time of ADD event driver will read sas device page0 using channel and FW ID provided in ADD Device event. Here in case of SATA drives, driver will see miss match in phyinfo->sas_address and latest sas address read from SAS DEVICE PAGE0 and eventually device won't be added to OS. Fix: When Driver read SAS DEVICE PAGE0, it can identify Device type looking at device_info. If device is SATA drive and sas address mismatch happens, Driver will do same stuffs which happened at the time of LINK UP to get correct piece of information from Pages. ( Find parent device and refresh parent device phys either HBA refresh/Exp refresh) Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com> Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'drivers/net/tsi108_eth.c')
0 files changed, 0 insertions, 0 deletions