From: Mario Limonciello <mario_limonciello@dell.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: 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: Tue, 19 May 2009 17:19:58 -0500 [thread overview]
Message-ID: <4A13308E.4040703@dell.com> (raw)
In-Reply-To: <200905200016.49110.oliver@neukum.org>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
Hi Oliver:
Oliver Neukum wrote:
> Am Dienstag, 19. Mai 2009 23:47:02 schrieb Mario Limonciello:
>
>
> That is correct the devices have been successfully resumed and thus are
> present. Generally the idea of suspened/resume is to have the same system
> after resumption. It is correct to not generate events. Usbcore cannot know
> that you use udev to switch the device from pure HID to HID + bluetooth.
>
>
Right, which makes sense.
>
> Yes, the question is whether it is the clean thing to do.
>
> Marcel, are the HID devices usable after hid2hci has run? Should we
> choose to not resume from power loss any hid device which hid2hci
> operated on?
>
> Regards
> Oliver
>
>
I can actually field this answer. Currently those HID devices have no
purpose after hid2hci has operated on them. If transitioned back into
full HID mode, then the mouse and keyboard HID devices can be functional.
Regards
--
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-19 22:20 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 [this message]
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
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=4A13308E.4040703@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 \
/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