Driver fix attempt #5

What the actual fuck. The same exact issue with the other driver except
this time, the code path is so clear, I can't even begin to imagine
where the problem lies. It *has* to be caused from
input_unregister_device. The input_device must not be configured
correctly... but with all my might, I cannot figure out what's wrong with it.