[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0551C926975A174EA8972327741C7889EE81189A@RS-MBS01.realsil.com.cn>
Date: Wed, 14 Aug 2019 07:33:20 +0000
From: 陆朱伟 <alex_lu@...lsil.com.cn>
To: Marcel Holtmann <marcel@...tmann.org>
CC: Johan Hedberg <johan.hedberg@...il.com>,
"linux-bluetooth@...r.kernel.org" <linux-bluetooth@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Max Chou <max.chou@...ltek.com>
Subject: 答复: [PATCH v2] Bluetooth: btusb: Fix suspend issue for Realtek devices
Hi Marcel,
Okay, I will send a version for bluetooth-next.
Thanks,
BRs.
> Subject: Re: [PATCH v2] Bluetooth: btusb: Fix suspend issue for Realtek devices
>
> Hi Alex,
>
> > From the perspective of controller, global suspend means there is no
> > SET_FEATURE (DEVICE_REMOTE_WAKEUP) and controller would drop the
> > firmware. It would consume less power. So we should not send this kind
> > of SET_FEATURE when host goes to suspend state.
> > Otherwise, when making device enter selective suspend, host should send
> > SET_FEATURE to make sure the firmware remains.
> >
> > Signed-off-by: Alex Lu <alex_lu@...lsil.com.cn>
> > ---
> > drivers/bluetooth/btusb.c | 34 ++++++++++++++++++++++++++++++----
> > 1 file changed, 30 insertions(+), 4 deletions(-)
>
> this one doesn’t apply cleanly to bluetooth-next. Can you please send a
> version that does.
>
> Regards
>
> Marcel
>
>
> ------Please consider the environment before printing this e-mail.
Powered by blists - more mailing lists