summaryrefslogtreecommitdiff
path: root/scripts/const_structs.checkpatch
diff options
context:
space:
mode:
authorStefan Eichenberger <[email protected]>2021-12-09 11:19:33 +0100
committerStefan Roese <[email protected]>2021-12-19 09:50:47 +0100
commitd61f3ee9bb032a3e708f17824f95f8c21e01939d (patch)
tree107fee84dbe75037db5c0602c9d47fd00734d077 /scripts/const_structs.checkpatch
parent574506c327318e82095122470d258da0be21b294 (diff)
arm: mvebu: a38x: serdes: fix serdes config for USB3
The electrical serdes configuration for USB3 expects an array as data argument. For USB3 the second value is used (see data_arr_idx = USB3 = 1). However, because only one value is inside the array mv_seq_exec is accessing an invalid element and the serdes is configured wrongly. This wrong initialization is leading to an unreliable detection mechanism for some USB3 devices. We were able to reproduce the issue regularly with an LTE modem from Sierra Wireless (SM7455) where it was not detected as USB3 device in 1/3 of all tests. This commit fixes the issue by setting data_arr_idx to 0. This is the same value as the original U-Boot from Marvell is using. There it is called FIRST_CELL which is a define for 0. See: https://github.com/MarvellEmbeddedProcessors/u-boot-marvell commit 56f963ce4c ("fix: serdes: a38x, a39x: Fix USB3 serdes DB initialization") Signed-off-by: Stefan Eichenberger <[email protected]> Signed-off-by: RenĂ© Straub <[email protected]> Reviewed-by: Stefan Roese <[email protected]>
Diffstat (limited to 'scripts/const_structs.checkpatch')
0 files changed, 0 insertions, 0 deletions