summaryrefslogtreecommitdiff
path: root/doc/develop/python_cq.rst
diff options
context:
space:
mode:
authorNeil Armstrong <[email protected]>2024-09-30 14:44:34 +0200
committerNeil Armstrong <[email protected]>2024-10-14 08:55:28 +0200
commit67e291d147cd40c9b638515dc1bfa3c52d390959 (patch)
tree9389f47aa8d8f4b2bbdb75db3b9e28ec5e7e19a7 /doc/develop/python_cq.rst
parent966d3bf431273d8f397271026f0a6d488b3c87fc (diff)
ufs: core: remove link_startup_again logic
The link_startup_again logic was added in Linux to handle device that were set in LinkDown state, which should not be the case since U-boot doesn't set LinkDown state are init, and Linux sets the device active in ufshcd_init() for the first link startup. ufshcd_set_ufs_dev_active(hba) is called at ufshcd_init() right before scheduling an ufshcd_async_scan that will call ufshcd_device_init() then ufshcd_link_startup(). The comment in probe says: /* * We are assuming that device wasn't put in sleep/power-down * state exclusively during the boot stage before kernel. * This assumption helps avoid doing link startup twice during * ufshcd_probe_hba(). */ we can assume the same from U-Boot. While it worked to far, it breaks link startup for Qualcomm Controllers v5, let's just remove the logic. Tested-by: Venkatesh Yadav Abbarapu <[email protected]> Tested-by: Julius Lehmann <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Neil Armstrong <[email protected]>
Diffstat (limited to 'doc/develop/python_cq.rst')
0 files changed, 0 insertions, 0 deletions