driver. Now there is (although it isn't very good),
so it would be legitimate to remove the !PM condition.
As far as I know, the only person who ever used the onetouch driver was
its author.
Alan Stern
On Thu, 27 Sep 2007, Oliver Neukum wrote:
> Am Donnerstag 27 September 2007 schrieb Alan Stern:
> > > mechanism the same way the version for generic hid does. In fact, it is
> > > only necessary because there's no nice API call for setting
> > > needs_remote_wa
On Thu, 27 Sep 2007, Oliver Neukum wrote:
> Am Donnerstag 27 September 2007 schrieb Alan Stern:
> > On Thu, 27 Sep 2007, Oliver Neukum wrote:
> >
> > > @@ -528,12 +537,20 @@ exit:
> > > static int atp_open(struct input_dev *input)
> > > {
> &g
usb_kill_urb(dev->urb);
> cancel_work_sync(&dev->work);
> dev->open = 0;
> + dev->intf->needs_remote_wakeup = 0;
> }
Doesn't atp_close() need to call usb_autopm_put_interface(), to balance
the usb_autopm_get_interface() call in atp_open()?
Alan Stern
acy support work with
> > both SMM and the Linux USBHID system trying to handle it?
> >
> Please tell me what I can do to help to debug this strange behaviour.
> Repuducing the USB resets is easy, but reproducing the PS/2 influence
> takes long, since its hardly visible.
My advice is don't do anything and don't worry about it. It really isn't
an important problem.
Alan Stern
On Fri, 16 Mar 2007, Dmitry Torokhov wrote:
> On 3/16/07, Alan Stern <[EMAIL PROTECTED]> wrote:
> > Take a look at the message below. It turned out that the USB errors went
> > away when Claas removed a USB extension cable, but that doesn't explain
> > the pec
Take a look at the message below. It turned out that the USB errors went
away when Claas removed a USB extension cable, but that doesn't explain
the peculiar keyboard-mouse interaction -- especially since it's a PS/2
keyboard. Any ideas?
Alan Stern
-- Forward
