From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dmitry Torokhov" Subject: Re: appletouch quirk doesn't run at resume Date: Wed, 28 Mar 2007 09:24:06 -0400 Message-ID: References: <1174078066.13341.279.camel@localhost.localdomain> <1174087552.13341.332.camel@localhost.localdomain> <45FBBDEA.9060708@m3y3r.de> <20070318004240.GO752@stusta.de> <45FD8CA3.10405@m3y3r.de> <4609866C.4060602@m3y3r.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline Sender: owner-linux-input@atrey.karlin.mff.cuni.cz List-Help: List-Owner: List-Post: List-Unsubscribe: To: Jiri Kosina Cc: Thomas Meyer , Jiri Kosina , Linux Kernel Mailing List , Adrian Bunk , Soeren Sonnenburg , linux-input@atrey.karlin.mff.cuni.cz, Peter Osterlund List-Id: linux-input@vger.kernel.org On 3/28/07, Jiri Kosina wrote: > On Tue, 27 Mar 2007, Thomas Meyer wrote: > > > It seems, that after the resume all usb devices gets removed and plug in > > again (virtually!). This results in a new input device name: > > Yes, this is what actually happens. JFYI see current thread on lkml which > is a bit realted - http://lkml.org/lkml/2007/3/27/149 if interested. > > > This change confuses the X synaptics driver: > > Touchpad no synaptics event device found (checked 11 nodes) > > Touchpad The /dev/input/event* device nodes seem to be missing > > (EE) xf86OpenSerial: Cannot open device /dev/input/event2 > > No such file or directory. > > (WW) Touchpad: cannot open input device > > One could say that the synaptics driver rightly complains about the > > missing event2 device! So is this a bug in the X synaptics driver? > > You can of course work this around by adding an udev rule such as > > SUBSYSTEM=="input",KERNEL=="event*",SYSFS{name}=="appletouch",SYMLINK+="input/appletouchpad" > > and the let Xorg use /dev/input/appletouchpad, which will always be a > symlink to the correct device. > I am not sure if this would help... According to the excerpt from X log synaptics driver attempted to scan evdev devices and locate the touchpad. However if this scan happen before udev had a chance to process the event and create new /dev/input/eventX device node it will fail. I wonder if we should adjust the X driver to spin for a couple of seconds in EventAutoDevProbe if the touchpad was already seen once... Peter? -- Dmitry