From: Jonathan Corbet <corbet@lwn.net>
To: Matthew Garrett <mjg59@srcf.ucam.org>
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 12:01:45 -0600 [thread overview]
Message-ID: <20120501120145.21f65ae2@lwn.net> (raw)
In-Reply-To: <20120501171901.GA26006@srcf.ucam.org>
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.
> 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".
FWIW, power/runtime_status reads "suspended" most of the time. By banging
on the keyboard I can get it to "active", but it goes back to "suspended"
even with continuous activity. Weirdly, the keyboard continues to work if
I keep hitting keys.
Thanks,
jon
next prev parent reply other threads:[~2012-05-01 18:01 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 [this message]
2012-05-01 18:31 ` Matthew Garrett
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=20120501120145.21f65ae2@lwn.net \
--to=corbet@lwn.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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.