at 22:17, Alan Stern wrote:
On Thu, 6 Jun 2019, Kai-Heng Feng wrote:
at 15:55, Kai-Heng Feng wrote:
at 18:22, Kai-Heng Feng wrote:
at 00:01, Kai-Heng Feng wrote:
On Jan 30, 2019, at 16:21, Greg KH wrote:
On Thu, Jan 24, 2019 at 02:16:43PM +0800, Kai-Heng Feng wrote:
The QCA Rome US
On Thu, 6 Jun 2019, Kai-Heng Feng wrote:
> at 15:55, Kai-Heng Feng wrote:
>
> > at 18:22, Kai-Heng Feng wrote:
> >
> >> at 00:01, Kai-Heng Feng wrote:
> >>
> On Jan 30, 2019, at 16:21, Greg KH wrote:
>
> On Thu, Jan 24, 2019 at 02:16:43PM +0800, Kai-Heng Feng wrote:
> > The
at 15:55, Kai-Heng Feng wrote:
at 18:22, Kai-Heng Feng wrote:
at 00:01, Kai-Heng Feng wrote:
On Jan 30, 2019, at 16:21, Greg KH wrote:
On Thu, Jan 24, 2019 at 02:16:43PM +0800, Kai-Heng Feng wrote:
The QCA Rome USB Bluetooth controller has several issues once LPM gets
enabled:
- Fails
> On Jan 30, 2019, at 16:21, Greg KH wrote:
>
> On Thu, Jan 24, 2019 at 02:16:43PM +0800, Kai-Heng Feng wrote:
>> The QCA Rome USB Bluetooth controller has several issues once LPM gets
>> enabled:
>> - Fails to get enumerated in coldboot. [1]
>> - Drains more power (~ 0.2W) when the system is
On Thu, Jan 24, 2019 at 02:16:43PM +0800, Kai-Heng Feng wrote:
> The QCA Rome USB Bluetooth controller has several issues once LPM gets
> enabled:
> - Fails to get enumerated in coldboot. [1]
> - Drains more power (~ 0.2W) when the system is in S5. [2]
> - Disappears after a warmboot. [2]
>
> The
The QCA Rome USB Bluetooth controller has several issues once LPM gets
enabled:
- Fails to get enumerated in coldboot. [1]
- Drains more power (~ 0.2W) when the system is in S5. [2]
- Disappears after a warmboot. [2]
The issue happens because the device lingers at LPM L1 in S5, so device
can't get
6 matches
Mail list logo