Hi Dmitry, >> I have tested the insertion/removel of 2 different drivers (keyboard >> and touchscreen), what I have seen is that the sequence in the number >> of the event is always different aty the time of registering them, I'd >> expect that if I remove a module, the event number is freed, making it >> available for the next time but this is not the case >> > > The number you are referring to is not "event number" but just a part of > input device name. It always monotonically increases and is not stable > across reboots. > ok >> Is there any specific function from the input subsystem to free it? > > No, as we do not track these numbers there is no way to "free" it. ok >> Do >> we have a limitation on the input subsystem? >> > > Not that I can see (at least not in this particular area ;) ). It would > be helpful to know what kind of issue you are trying to solve. There was an issue of sysfs name already registered at the time of inserting the module, this is my fix http://dev.omapzoom.org/?p=santosh/kernel-omap4-base.git;a=commitdiff;h=7515b03817f0b590085332cbdec6cb0f592dd6cb but in my final testing I realized that the "number" was increasing, then I took a touchscreen driver and test again insertion/removal seeing same behaviour... So having above information as background I see this is an expected scenario, no more issue for now... thanks Dmitry! Best Regards Abraham -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
