From: Mario Limonciello <mario_limonciello@dell.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oliver@neukum.org>,
linux-usb@vger.kernel.org, Matthew Garrett <mjg59@srcf.ucam.org>,
Marcel Holtmann <marcel@holtmann.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
Date: Wed, 20 May 2009 12:52:07 -0500 [thread overview]
Message-ID: <4A144347.80303@dell.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0905201010260.2914-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
Hi Alan:
Alan Stern wrote:
> On Wed, 20 May 2009, Oliver Neukum wrote:
>
>
>
> That's okay. Inelegant, perhaps, but workable. Besides, as we see
> below, the new rule would have to do more than the old rule.
>
>
I agree this is a rather inelegant solution. A new rule would have to
be added to hid2hci then. It's much more preferable to be able to fix
kernel space from mucking up the device. Is there a way to mark a
device to /not/ run reset-resume after S3?
>
> Does that create the same removal event? If it does then you wouldd be
> in an unfortunate state. The script would have to check somehow
> whether the removal was deliberate or spontaneous.
>
Yes it does create the same removal event when you switch to HID mode.
I don't know of any way that you can calculate if the switch was
intentional.
--
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@dell.com
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2009-05-20 17:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 20:12 [PATCH] Explicitly disable BT radio using rfkill interface on suspend Mario Limonciello
2009-05-18 21:02 ` Matthew Garrett
2009-05-18 21:36 ` Mario Limonciello
2009-05-19 5:03 ` Matthew Garrett
2009-05-19 5:14 ` Marcel Holtmann
2009-05-19 6:27 ` Oliver Neukum
2009-05-19 6:45 ` Marcel Holtmann
2009-05-19 7:36 ` Oliver Neukum
2009-05-19 9:06 ` Matthew Garrett
2009-05-19 12:47 ` Oliver Neukum
2009-05-19 12:58 ` Matthew Garrett
2009-05-19 16:30 ` Mario Limonciello
2009-05-19 16:33 ` Matthew Garrett
2009-05-19 16:52 ` Mario Limonciello
2009-05-19 19:58 ` Oliver Neukum
2009-05-19 20:36 ` Mario Limonciello
2009-05-19 21:26 ` Oliver Neukum
2009-05-19 21:47 ` Mario Limonciello
2009-05-19 22:16 ` Oliver Neukum
2009-05-19 22:19 ` Mario Limonciello
2009-05-20 2:17 ` Alan Stern
2009-05-20 12:29 ` Oliver Neukum
2009-05-20 14:17 ` Alan Stern
2009-05-20 17:52 ` Mario Limonciello [this message]
2009-05-20 18:31 ` Alan Stern
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=4A144347.80303@dell.com \
--to=mario_limonciello@dell.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mjg59@srcf.ucam.org \
--cc=oliver@neukum.org \
--cc=stern@rowland.harvard.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox