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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 19 May 2009 13:58:53 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	Marcel Holtmann <marcel@...tmann.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

On Tue, May 19, 2009 at 02:47:33PM +0200, Oliver Neukum wrote:
> Am Dienstag, 19. Mai 2009 11:06:12 schrieb Matthew Garrett:
> > On Mon, May 18, 2009 at 10:14:24PM -0700, Marcel Holtmann wrote:
> > > Hi Matthew,
> > >
> > > > 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.
> >
> > If the device is getting removed from underneath you, why isn't hid2hci
> > being run again when it reappears as the hid device?
> 
> udev triggers exactly that.

It doesn't seem to for Mario, otherwise this patch wouldn't change 
anything.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/