Il 23/06/22 02:35, sean.wang@xxxxxxxxxxxx ha scritto:
From: Sean Wang <sean.wang@xxxxxxxxxxxx> Reduce the mutex lock scope for reset to get rid of possible task hung e.g wpa_supplicant and to allow the user-space process to keep running during we need more retries to complete the reset.
To actually, effectively, reduce the chance to get a hung task, and also to improve the general responsiveness, I think that the best way would be to manage the locking inside of the reset callback(s) for each dev/bus. This is especially because some of these reset functions (like the SDIO one) may end up waiting for more than *two seconds*. However, I get that this proposal requires way more effort, and this commit will anyway improve the situation as it is... so, you get my: Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@xxxxxxxxxxxxx>
Suggested-by: YN Chen <YN.Chen@xxxxxxxxxxxx> Signed-off-by: Sean Wang <sean.wang@xxxxxxxxxxxx>
