diff options
| author | 2026-06-25 05:13:04 -0700 | |
|---|---|---|
| committer | 2026-07-16 22:26:54 -0400 | |
| commit | 4bd0875b7e571eeeed45fdab52672b850c1845a5 (patch) | |
| tree | 82a93894475c589ef4173420095f8e9093f827b8 /tools/lib/python/kdoc/python_version.py | |
| parent | scsi: ufs: ufs-qcom: Restore TX Equalization settings on FOM failure (diff) | |
scsi: ufs: core: Tolerate RX_FOM read failures in TX EQTR
ufshcd_get_rx_fom() aborted TX EQTR when a per-lane RX_FOM DME read failed.
That makes the whole training flow fragile even though these reads can be
treated as best effort.
Keep TX EQTR running by logging RX_FOM read failures and continuing. Make
failed lanes deterministic by initializing each lane FOM to 0 before
reading and only updating it when the DME read succeeds. This avoids
propagating stale or uninitialized values into EQTR evaluation.
Also update the kerneldoc return description to match behavior: RX_FOM DME
read failures are handled as warnings, while get_rx_fom() vops failures are
still propagated to the caller.
Signed-off-by: Can Guo <can.guo@oss.qualcomm.com>
Reviewed-by: Peter Wang <peter.wang@mediatek.com>
Reviewed-by: Bean Huo <beanhuo@micron.com>
Reviewed-by: Ziqi Chen <ziqi.chen@oss.qualcomm.com>
Link: https://patch.msgid.link/20260625121306.1655467-3-can.guo@oss.qualcomm.com
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions
