[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180507130638.3516-1-ville.syrjala@linux.intel.com>
Date: Mon, 7 May 2018 16:06:38 +0300
From: Ville Syrjala <ville.syrjala@...ux.intel.com>
To: linux-bluetooth@...r.kernel.org
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Marcel Holtmann <marcel@...tmann.org>,
Kay Sievers <kay.sievers@...y.org>,
systemd-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
Ville Syrjälä
<ville.syrjala@...ux.intel.com>
Subject: [PATCH bluez] hid2hci: Fix udev rules for linux-4.14+
From: Ville Syrjälä <ville.syrjala@...ux.intel.com>
Since commit 1455cf8dbfd0 ("driver core: emit uevents when
device is bound to a driver") the kernel started emitting
"bound" and "unbound" uevents which confuse the hid2hci
udev rules.
The symptoms on an affected machine (Dell E5400 in my case)
include bluetooth devices not appearing and udev hogging
the cpu as it's busy processing a constant stream of these
"bound"+"unbound" uevents.
Change the udev rules only kick in for an "add" event.
This seems to cure my machine at least.
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Marcel Holtmann <marcel@...tmann.org>
Cc: Kay Sievers <kay.sievers@...y.org>
Cc: systemd-devel@...ts.freedesktop.org
Cc: linux-kernel@...r.kernel.org
Cc: linux-bluetooth@...r.kernel.org
Signed-off-by: Ville Syrjälä <ville.syrjala@...ux.intel.com>
---
tools/hid2hci.rules | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/hid2hci.rules b/tools/hid2hci.rules
index db6bb03d2ef3..daa381d77387 100644
--- a/tools/hid2hci.rules
+++ b/tools/hid2hci.rules
@@ -1,6 +1,6 @@
# do not edit this file, it will be overwritten on update
-ACTION=="remove", GOTO="hid2hci_end"
+ACTION!="add", GOTO="hid2hci_end"
SUBSYSTEM!="usb*", GOTO="hid2hci_end"
# Variety of Dell Bluetooth devices - match on a mouse device that is
--
2.16.1
Powered by blists - more mailing lists