From: Marcel Holtmann <marcel@holtmann.org>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-usb@vger.kernel.org, Matthew Garrett <mjg59@srcf.ucam.org>,
Mario Limonciello <mario_limonciello@dell.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend
Date: Mon, 18 May 2009 23:45:12 -0700 [thread overview]
Message-ID: <1242715512.3147.6.camel@localhost.localdomain> (raw)
In-Reply-To: <200905190827.52541.oliver@neukum.org>
Hi Oliver,
> > > > When coming out of S3 if the killswitch isn't activated, the logical
> > > > USB mouse isn't coldplugged again preventing the udev rule from being
> > > > matched upon. You can manually run hid2hci and the device will switch
> > > > modes.
> > >
> > > Ok. I don't think the right way to implement this is forcing dell-laptop
> > > to simulate an unplug. The HCI driver should be responsible for saving
> > > and restoring state of the device in its suspend/resume method.
> >
> > what do you expect the generic USB driver to do? I don't see anything we
> > can do about it, if the device gets removed from underneath us.
>
> In order to do this we'd have to put hid2hci into usbcore and maintain
> a list of devices it should operate on.
you know that hid2hci is a user space utility.
Regards
Marcel
next prev parent reply other threads:[~2009-05-19 6:45 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 [this message]
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
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=1242715512.3147.6.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario_limonciello@dell.com \
--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