diff options
| author | John Garry <john.garry@huawei.com> | 2016-09-06 18:36:21 +0300 |
|---|---|---|
| committer | Martin K. Petersen <martin.petersen@oracle.com> | 2016-09-14 19:54:18 +0300 |
| commit | 44c4abe08f224817747795fb8d0677888166e4cd (patch) | |
| tree | 73b5dc7dc69982586483747df5db29f1714ede4d /scripts | |
| parent | d82debecf29b4d89e2d17a52dc32c745ba97c999 (diff) | |
| download | linux-44c4abe08f224817747795fb8d0677888166e4cd.tar.xz | |
scsi: hisi_sas: fix HBA SAS addr endianness for v1 hw
The endianness for the SAS address in the TX_ID_DWORD registers is set
incorrectly. We see errors like this in the boot log for v2 hw (which
would have the same issue as v1 hw):
[ 7.583284] sas: target proto 0x0 at 50000d1108e7923f:0x1f not handled
This is due to the host SAS addr not matching the PHY SAS addr in the
expander host-attached phy discovery responses.
To fix, we byte swap the SAS addr from BE to LE (which is the endianness
of the SAS controller).
Signed-off-by: John Garry <john.garry@huawei.com>
Signed-off-by: Xiang Chen <chenxiang66@hisilicon.com>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
