linux-kernel - Re: [PATCH] Explicitly disable BT radio using rfkill interface on suspend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1242715512.3147.6.camel@localhost.localdomain>
Date:	Mon, 18 May 2009 23:45:12 -0700
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	linux-usb@...r.kernel.org, Matthew Garrett <mjg59@...f.ucam.org>,
	Mario Limonciello <mario_limonciello@...l.com>,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Explicitly disable BT radio using rfkill interface on
 suspend

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/