LKML Archive on
help / color / mirror / Atom feed
From: Kirill Elagin <>
To: Oliver Neukum <>
Subject: Re: USB autosuspend causing trouble with bluetooth
Date: Tue, 20 Jan 2015 18:58:13 +0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Jan 20, 2015 at 5:06 PM, Oliver Neukum <> wrote:
> On Tue, 2015-01-20 at 16:18 +0400, Kirill Elagin wrote:
>> I use a Logitech wireless keyboard (with a Unifying receiver) and it
>> keeps working fine even with `auto`.
>> That is, everything is OK if the receiver is plugged before
>> `power/control` is switched to `auto`.
> Wait. There is no power/control file for the receiver before
> you plug it in. We are having a very big misunderstanding here.

Sorry for not being clear. I was referring to `power/control` of the
USB-device itself except for the cases when I was talking about
hot-plugging issues — in those cases I was referring to the
`power/control` of the root hub.

I might be using terminology in a wrong way. By `power/control` of a
root hub I mean `/sys/bus/usb/devices/usb<bus_number>/power/control`
and by `power/control` of a device I mean

>> But if I first set it to `auto`, then plug the receiver in, it is not
>> detected (nothing in dmesg). Kernel
>> detects it as soon as I `echo on` to the relevant `power/control`.
> Are you on power/control for the device or the port?
> If you are using the port's control file you might be switching
> on Port Power Off. Then of course the port will not process
> hotplugs. Please clarify!

In this particular case I was talking about the `power/control` of the root hub.

`laptop-mode-tools` by default writes `auto` to `power/control` of
_all_ the USB devices, root hubs included (even when on AC). Is it
really expected that kernel might completely power off the physical
USB port? Sounds weird.

Here is an even more strange thing. First I set all the USB power
management to the defaults (that is, `auto` for all the usb devices
including root hubs). Again, the keyboard keeps working and as soon as
I unplug the receiver kernel says the device was disconnected. Now if
I plug the receiver back nothing happens. _But_ if I plug a flash
drive in the save physical port it gets detected. So, I tried a number
of other usb devices and it totally looks like USB2.0 ones are
properly hot-plugged while USB1.1 devices are not. Does this sound to
you like a bug in my laptop's hardware?

  reply	other threads:[~2015-01-20 14:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-18 13:30 Kirill Elagin
2015-01-20 11:03 ` Oliver Neukum
2015-01-20 12:18   ` Kirill Elagin
2015-01-20 12:34     ` Kirill Elagin
2015-01-20 14:06     ` Oliver Neukum
2015-01-20 14:58       ` Kirill Elagin [this message]
2015-01-20 17:41         ` Oliver Neukum
2015-01-20 19:25           ` Kirill Elagin
2015-01-20 21:47             ` Oliver Neukum
2015-01-24  9:55               ` Kirill Elagin
2015-01-26 17:00                 ` Kirill Elagin
2015-01-27 18:00                   ` Oliver Neukum

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \
    --subject='Re: USB autosuspend causing trouble with bluetooth' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).