On Mon, Mar 06, 2023 at 05:07:07PM +0800, Archie Pusaka wrote: > From: Archie Pusaka <apusaka@xxxxxxxxxxxx> > > Currently, when we initiate disconnection, we will wait for the peer's > reply unless when we are suspending, where we fire and forget the > disconnect request. > > A similar case is when adapter is powering off. However, we still wait > for the peer's reply in this case. Therefore, if the peer is > unresponsive, the command will time out and the power off sequence > will fail, causing "bluetooth powered on by itself" to users. > > This patch makes the host doesn't wait for the peer's reply when the > disconnection reason is powering off. > > Signed-off-by: Archie Pusaka <apusaka@xxxxxxxxxxxx> > Reviewed-by: Abhishek Pandit-Subedi <abhishekpandit@xxxxxxxxxx> Reviewed-by: Simon Horman <simon.horman@xxxxxxxxxxxx>
