[systemd-devel] [PATCH] rules: don't enable usb pm for Avocent devices

[Tom Hirst]

> 
> On Wed, Jun 25, 2014 at 11:57:11AM +0000, Tom Hirst wrote:
> > The Avocent KVM over IP devices doesn't work correctly with USB power
> > management enabled.
> > ---
> >  rules/42-usb-hid-pm.rules | 4 ----
> >  1 file changed, 4 deletions(-)
> >
> > diff --git a/rules/42-usb-hid-pm.rules b/rules/42-usb-hid-pm.rules
> > index c675b5b..4c300da 100644
> > --- a/rules/42-usb-hid-pm.rules
> > +++ b/rules/42-usb-hid-pm.rules
> > @@ -12,10 +12,6 @@ ACTION=="add", SUBSYSTEM=="usb",
> > ATTR{product}=="QEMU USB Mouse", ATTR{serial}!=  ACTION=="add",
> SUBSYSTEM=="usb", ATTR{product}=="QEMU USB Tablet",
> ATTR{serial}!="1", TEST=="power/control", ATTR{power/control}="auto"
> >  ACTION=="add", SUBSYSTEM=="usb", ATTR{product}=="QEMU USB
> Keyboard", ATTR{serial}!="1", 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"
> 
> Is it possible to blacklist the specific idProduct only?
> 
> Zbyszek

In theory, yes, but I don't have access to the device at the moment to get the
idProduct.

However,  the list generally seems to be a whitelist, so would the correct solution 
not be to only add the specific idProduct (s) for the devices where it does work?

Also, if you do decide to apply this it is probably be a candidate for stable.

Tom