Re: [REGRESSION] "bind" a device to a driver doesn't not work anymore

[Dmitry Torokhov <dmitry.torokhov@gmail.com>]

On Saturday 10 October 2009 08:00:29 pm Greg KH wrote:
> On Sun, Oct 11, 2009 at 02:04:02AM +0200, ?ric Piel wrote:
> > Hello,
> >
> > After a suspend, I used to do this (to get the PS2 keyboard working
> > again), and it used to work fine:
> > echo -n "i8042" > /sys/bus/platform/drivers/i8042/unbind ; sleep 1 ; echo
> > -n "i8042" > /sys/bus/platform/drivers/i8042/bind
> >
> > Unfortunately since 2.6.32-rc1, the unbind works fine, but the bind
> > returns a "no such device" error now (and the binding is not done). After
> > that, additional unbinds also report the error. I think 2.6.31 worked
> > fine. Any idea what's going wrong?
> 
> Odd.  Any chance you can run 'git bisect' to figure out which patch
> might have caused it?

I8042 has been converted to use platform_driver_probe() - we are creating 
platform device and platform driver together, there is no chance that some 
other device might be driven by i8042 driver.

Eric, do you still need to fiddle with i8042 to get your keyboard working with 
2.6.32-rc3? We need to make sure that resube works without users needing to 
mess with bind/unbind.

-- 
Dmitry