mirror of
https://source.denx.de/u-boot/u-boot.git
synced 2026-05-05 20:56:12 +02:00
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 <venkatesh.abbarapu@amd.com>
Tested-by: Julius Lehmann <lehmanju@devpi.de>
Link: https://lore.kernel.org/r/20240930-topic-ufs-enhancements-v3-12-58234f84ab89@linaro.org
Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
This commit is contained in:
parent
966d3bf431
commit
67e291d147
@ -462,9 +462,7 @@ static int ufshcd_link_startup(struct ufs_hba *hba)
|
||||
{
|
||||
int ret;
|
||||
int retries = DME_LINKSTARTUP_RETRIES;
|
||||
bool link_startup_again = true;
|
||||
|
||||
link_startup:
|
||||
do {
|
||||
ufshcd_ops_link_startup_notify(hba, PRE_CHANGE);
|
||||
|
||||
@ -490,12 +488,6 @@ link_startup:
|
||||
/* failed to get the link up... retire */
|
||||
goto out;
|
||||
|
||||
if (link_startup_again) {
|
||||
link_startup_again = false;
|
||||
retries = DME_LINKSTARTUP_RETRIES;
|
||||
goto link_startup;
|
||||
}
|
||||
|
||||
/* Mark that link is up in PWM-G1, 1-lane, SLOW-AUTO mode */
|
||||
ufshcd_init_pwr_info(hba);
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user