From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mario Limonciello Date: Tue, 14 Jul 2009 16:40:20 +0000 Subject: Re: [PATCH] Explicitly disable BT radio using rfkill interface on Message-Id: <4A5CB4F4.1090905@dell.com> MIME-Version: 1 Content-Type: multipart/mixed; boundary="------------enig974D5E9C8D5E6B7B75C0B37C" List-Id: References: <4A4A8B6D.3060509@dell.com> In-Reply-To: <4A4A8B6D.3060509@dell.com> To: linux-hotplug@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig974D5E9C8D5E6B7B75C0B37C Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Alan: Alan Stern wrote: > Right. The log clearly shows that HID devices 4-1.1 and 4-1.2 survive = > the suspend-resume cycle intact, whereas the BT device 4-1.3 is gone. > > Since the BT device was created by means of a userspace script in the=20 > first place, it seems logical that a userspace script should respond to= =20 > the uevent announcing its disappearance and try to bring it back to=20 > life. > > Last I heard, you had created a udev rule which was supposed to match > the removal event for the BT device, but which udev wasn't executing. = > Is that still the case? If it is, you should post the rule together > with the udev log for a resume. Maybe somebody will be able to figure = > out why the rule isn't being executed. > =20 Yeah, Kay already identified why the rule wasn't being executed. It was reliant on properties of the device that aren't cached in the udev databa= se. > Also, I noticed that your C program for reviving the BT device seemed > more complex than necessary. You should know beforehand that if the BT= > device's path is 4-1.3 then the corresponding mouse device's path will > be 4-1.2 (just decrement the last byte of the pathname). You can then > match this device up with libusb by reading the busnum and devnum > attributes from the sysfs directory. > =20 I wasn't sure I wanted to jump to this conclusion as I can't predict if this will change for future hardware that supports these features. > Alan Stern > > =20 I'm at a loss at what else can really be done from userspace. If I can't match the device on removal and send it to the userspace app, not sure how else it can be revived. --=20 Mario Limonciello *Dell | Linux Engineering* mario_limonciello@dell.com --------------enig974D5E9C8D5E6B7B75C0B37C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpctPQACgkQ2CrZjkA73Yt1UACghlZyIr3v2xv5q6enKAxoWYl8 bh0Anj9PsMUcZeEkQXvtEWLnTru1Kr7W =azcS -----END PGP SIGNATURE----- --------------enig974D5E9C8D5E6B7B75C0B37C--