systemd-stable/rules/42-usb-hid-pm.rules

# do not edit this file, it will be overwritten on update
#
# Enable autosuspend for qemu emulated usb hid devices

# Note that there are buggy qemu versions which advertise remote
# wakeup support but don't actually implement it correctly.  This
# is the reason why we need a match for the serial number here.
# The serial number "42" is used to tag the implementations where
# remote wakeup is working.
ACTION=="add", SUBSYSTEM=="usb", ATTR{product}=="QEMU USB Mouse", ATTR{serial}=="42", TEST=="power/control", ATTR{power/control}="auto"
ACTION=="add", SUBSYSTEM=="usb", ATTR{product}=="QEMU USB Tablet", ATTR{serial}=="42", TEST=="power/control", ATTR{power/control}="auto"
ACTION=="add", SUBSYSTEM=="usb", ATTR{product}=="QEMU USB Keyboard", ATTR{serial}=="42", TEST=="power/control", ATTR{power/control}="auto"

# Catch-all for Avocent HID devices. Keyed off interface in order to only
# trigger on HID class devices.
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0624", ATTR{bInterfaceClass}=="03", TEST=="../power/control", ATTR{../power/control}="auto"

# Dell DRAC 4
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="413c", ATTR{idProduct}=="2500", TEST=="power/control", ATTR{power/control}="auto"

# Dell DRAC 5
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="413c", ATTR{idProduct}=="0000", TEST=="power/control", ATTR{power/control}="auto"

# IBM remote access
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="04b3", ATTR{idProduct}=="4001", TEST=="power/control", ATTR{power/control}="auto"
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="04b3", ATTR{idProduct}=="4002", TEST=="power/control", ATTR{power/control}="auto"
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="04b3", ATTR{idProduct}=="4012", TEST=="power/control", ATTR{power/control}="auto"

# Raritan Computer, Inc KVM.
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="14dd", ATTR{idProduct}=="0002", TEST=="power/control", ATTR{power/control}="auto"

# USB HID devices that are internal to the machine should also be safe to autosuspend

ACTION=="add", SUBSYSTEM=="usb", SUBSYSTEMS=="usb", ATTRS{removable}=="removable", GOTO="usb_hid_pm_end"
ACTION=="add", SUBSYSTEM=="usb", SUBSYSTEMS=="usb", ATTRS{removable}=="unknown", GOTO="usb_hid_pm_end"

ACTION=="add", SUBSYSTEM=="usb", ATTR{bInterfaceClass}=="03", ATTRS{removable}=="fixed", TEST=="../power/control", ATTR{../power/control}="auto"

LABEL="usb_hid_pm_end"
rules: usb-hid-pm - remove AMI devices On Thu, Dec 6, 2012 at 9:20 AM, Robert Milasan <rmilasan@suse.com> wrote: > It seems that the added rules: > > ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="046b", > ATTR{idProduct}=="ff10", TEST=="power/control", > ATTR{power/control}="auto" > > creates problems for people with Supermicro X8ST3 mb (and maybe > other Supermicro mb's) and renders the KVM-over-IP unusable, at BIOS > and GRUB the KVM works perfectly, but after that the device is unusable. > > Dropping the rule fixes the issue. > > Reference bug: https://bugzilla.novell.com/show_bug.cgi?id=792576 2012-12-07 00:48:49 +04:00			`# do not edit this file, it will be overwritten on update`
rules: Enable USB autosuspend on more USB HID devices Many servers will be connected to KVMs or include iLO support, and this is often presented as a set of USB input devices. Enabling autosuspend on these allows the USB hardware to be powered down, avoiding unnecessary wakeups and power consumption. The input devices will be self powered, so there's no risk of losing input events as there would be for real input devices. The same is true of USB input devices that are built into the system. 2012-03-12 23:45:26 +04:00			`#`
rules: usb-hid-pm - remove AMI devices On Thu, Dec 6, 2012 at 9:20 AM, Robert Milasan <rmilasan@suse.com> wrote: > It seems that the added rules: > > ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="046b", > ATTR{idProduct}=="ff10", TEST=="power/control", > ATTR{power/control}="auto" > > creates problems for people with Supermicro X8ST3 mb (and maybe > other Supermicro mb's) and renders the KVM-over-IP unusable, at BIOS > and GRUB the KVM works perfectly, but after that the device is unusable. > > Dropping the rule fixes the issue. > > Reference bug: https://bugzilla.novell.com/show_bug.cgi?id=792576 2012-12-07 00:48:49 +04:00			`# Enable autosuspend for qemu emulated usb hid devices`

rules: Enable USB autosuspend on more USB HID devices Many servers will be connected to KVMs or include iLO support, and this is often presented as a set of USB input devices. Enabling autosuspend on these allows the USB hardware to be powered down, avoiding unnecessary wakeups and power consumption. The input devices will be self powered, so there's no risk of losing input events as there would be for real input devices. The same is true of USB input devices that are built into the system. 2012-03-12 23:45:26 +04:00			`# Note that there are buggy qemu versions which advertise remote`
			`# wakeup support but don't actually implement it correctly. This`
			`# is the reason why we need a match for the serial number here.`
			`# The serial number "42" is used to tag the implementations where`
			`# remote wakeup is working.`
			`ACTION=="add", SUBSYSTEM=="usb", ATTR{product}=="QEMU USB Mouse", ATTR{serial}=="42", TEST=="power/control", ATTR{power/control}="auto"`
			`ACTION=="add", SUBSYSTEM=="usb", ATTR{product}=="QEMU USB Tablet", ATTR{serial}=="42", TEST=="power/control", ATTR{power/control}="auto"`
			`ACTION=="add", SUBSYSTEM=="usb", ATTR{product}=="QEMU USB Keyboard", ATTR{serial}=="42", TEST=="power/control", ATTR{power/control}="auto"`

			`# Catch-all for Avocent HID devices. Keyed off interface in order to only`
			`# trigger on HID class devices.`
			`ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="0624", ATTR{bInterfaceClass}=="03", TEST=="../power/control", ATTR{../power/control}="auto"`

			`# Dell DRAC 4`
			`ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="413c", ATTR{idProduct}=="2500", TEST=="power/control", ATTR{power/control}="auto"`

			`# Dell DRAC 5`
			`ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="413c", ATTR{idProduct}=="0000", TEST=="power/control", ATTR{power/control}="auto"`

			`# IBM remote access`
			`ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="04b3", ATTR{idProduct}=="4001", TEST=="power/control", ATTR{power/control}="auto"`
			`ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="04b3", ATTR{idProduct}=="4002", TEST=="power/control", ATTR{power/control}="auto"`
			`ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="04b3", ATTR{idProduct}=="4012", TEST=="power/control", ATTR{power/control}="auto"`

			`# Raritan Computer, Inc KVM.`
rules: fix typo in 42-usb-hid-pm.rules <arjan> can you open the 42-usb-hid-pm.rules file <arjan> and go to line 46 <arjan> and tell me why ATTR{idProduct}="0002" only has one = and not two (e.g. == ) ? <kay> arjan: yep <kay> arjan: bug 2012-07-14 02:50:49 +04:00			`ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="14dd", ATTR{idProduct}=="0002", TEST=="power/control", ATTR{power/control}="auto"`
rules: Enable USB autosuspend on more USB HID devices Many servers will be connected to KVMs or include iLO support, and this is often presented as a set of USB input devices. Enabling autosuspend on these allows the USB hardware to be powered down, avoiding unnecessary wakeups and power consumption. The input devices will be self powered, so there's no risk of losing input events as there would be for real input devices. The same is true of USB input devices that are built into the system. 2012-03-12 23:45:26 +04:00
			`# USB HID devices that are internal to the machine should also be safe to autosuspend`
rules: Limit USB autosuspend on USB HID devices Some USB ports on external hubs may be reported as "fixed". We only want to auto-enable this on ports that are internal to the machine, so check the parent state as well. 2012-05-25 18:27:25 +04:00
			`ACTION=="add", SUBSYSTEM=="usb", SUBSYSTEMS=="usb", ATTRS{removable}=="removable", GOTO="usb_hid_pm_end"`
Drop trailing whitespace 2013-03-23 01:51:52 +04:00			`ACTION=="add", SUBSYSTEM=="usb", SUBSYSTEMS=="usb", ATTRS{removable}=="unknown", GOTO="usb_hid_pm_end"`
rules: Limit USB autosuspend on USB HID devices Some USB ports on external hubs may be reported as "fixed". We only want to auto-enable this on ports that are internal to the machine, so check the parent state as well. 2012-05-25 18:27:25 +04:00
rules: Enable USB autosuspend on more USB HID devices Many servers will be connected to KVMs or include iLO support, and this is often presented as a set of USB input devices. Enabling autosuspend on these allows the USB hardware to be powered down, avoiding unnecessary wakeups and power consumption. The input devices will be self powered, so there's no risk of losing input events as there would be for real input devices. The same is true of USB input devices that are built into the system. 2012-03-12 23:45:26 +04:00			`ACTION=="add", SUBSYSTEM=="usb", ATTR{bInterfaceClass}=="03", ATTRS{removable}=="fixed", TEST=="../power/control", ATTR{../power/control}="auto"`
rules: Limit USB autosuspend on USB HID devices Some USB ports on external hubs may be reported as "fixed". We only want to auto-enable this on ports that are internal to the machine, so check the parent state as well. 2012-05-25 18:27:25 +04:00
rules: fix typo in 42-usb-hid-pm.rules <arjan> can you open the 42-usb-hid-pm.rules file <arjan> and go to line 46 <arjan> and tell me why ATTR{idProduct}="0002" only has one = and not two (e.g. == ) ? <kay> arjan: yep <kay> arjan: bug 2012-07-14 02:50:49 +04:00			`LABEL="usb_hid_pm_end"`