On 24 Jun 05:06 PM, Darren Etheridge wrote:
On 06/17/2014 09:17 AM, Guido Martínez wrote:
The TI tilcdc driver is designed with a notion of submodules. Currently,
at unload time, these submodules are iterated and destroyed.
Now that the tilcdc remove order is fixed, this can be handled
Guido,
On 06/17/2014 09:17 AM, Guido Martínez wrote:
The TI tilcdc driver is designed with a notion of submodules. Currently,
at unload time, these submodules are iterated and destroyed.
Now that the tilcdc remove order is fixed, this can be handled perfectly
I am not sure I understand the
On Tue, Jun 24, 2014 at 05:06:24PM -0500, Darren Etheridge wrote:
Guido,
On 06/17/2014 09:17 AM, Guido Martínez wrote:
The TI tilcdc driver is designed with a notion of submodules. Currently,
at unload time, these submodules are iterated and destroyed.
Now that the tilcdc remove order is
The TI tilcdc driver is designed with a notion of submodules. Currently,
at unload time, these submodules are iterated and destroyed.
Now that the tilcdc remove order is fixed, this can be handled perfectly
by the kernel using the device infrastructure, since each submodule
is a kernel driver
