On 5/11/2012 12:53 AM, Ge Gao wrote:
Dear all,
I am building my IIO driver as a module and will
constantly need to use "insmod" and "rmmod" to install it and remove it
due to development. However, I found that if I write anything to the
"trigger/current_trigger", it will not be able to remove it. The error
code is (11). Even I write "null" to it, it will not be able to be
removed.
However, If I don't write anything to it, just insmod and rmmod, it will
be remove successfully. Any idea what could cause this problem? I followed
what is in the IIO subsystem driver to write my driver. I can post it if
anyone want to take a look.
Hi Ge,
I'm afraid I won't be able to do any testing until at least tomorrow.
There are a few things that could give more information though in the
meantime:
* Could you try the above, but note down the reference counts that
lsmod will give you for the various drivers at each step of the
process. (before connecting the trigger, whilst it is connected and upon
disconnecting).
* Is there anything left when you read 'current_trigger' after writing
an invalid name to it?
* Are you using an existing trigger or is it also part of you driver?
Having the source code when I dig futher into this would also be helpful.
Anyone else seen anything similar? I haven't run any removal hammering
tests for a month or so, so something might have slipped into the core...
Jonathan
Thanks.
Ge
--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-iio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
