From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-bluetooth@vger.kernel.org
Subject: Re: [now bisected] Weird bluetooth keyboard regression - just me?
Date: Tue, 1 May 2012 19:31:49 +0100 [thread overview]
Message-ID: <20120501183149.GA28536@srcf.ucam.org> (raw)
In-Reply-To: <20120501120145.21f65ae2@lwn.net>
On Tue, May 01, 2012 at 12:01:45PM -0600, Jonathan Corbet wrote:
> On Tue, 1 May 2012 18:19:01 +0100
> Matthew Garrett <mjg59@srcf.ucam.org> wrote:
>
> > On its own, this should do precisely nothing.
>
> Nonetheless, at the previous patch
> (0846e7e9856c0928223447d9349a877202a63f24, usb: Add support for indicating
> whether a port is removable) things work. With this one, they don't.
The patch just exports an attribute, so it's something then acting on
that attribute...
> > What userspace are you
> > running, and what does the removable node in the sysfs entry for the
> > dongle's USB device say?
>
> It's Rawhide, updated yesterday. "Removable" says "fixed".
Ok, well that's the problem. udev is seeing "fixed" and enabling
autosuspend. Is this really bluetooth, or does it appear as a USB HID
device? Can you send lsusb -v?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2012-05-01 18:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 13:37 Weird bluetooth keyboard regression - just me? Jonathan Corbet
2012-05-01 16:00 ` Gustavo Padovan
2012-05-01 17:01 ` [now bisected] " Jonathan Corbet
2012-05-01 17:19 ` Matthew Garrett
2012-05-01 18:01 ` Jonathan Corbet
2012-05-01 18:31 ` Matthew Garrett [this message]
2012-05-01 18:39 ` Jonathan Corbet
2012-05-01 18:54 ` Matthew Garrett
2012-05-01 19:27 ` Matthew Garrett
2012-05-01 23:24 ` Jonathan Corbet
2012-05-02 21:50 ` Matthew Garrett
2012-05-02 22:04 ` Jonathan Corbet
2012-05-02 22:27 ` Matthew Garrett
2012-05-10 22:51 ` Jonathan Corbet
2012-05-14 13:25 ` Matthew Garrett
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120501183149.GA28536@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=corbet@lwn.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.