5 Sep
2017
5 Sep
'17
9:40 a.m.
Hi Takashi-san
Thank you for your feedback
This isn't something you shouldn't fiddle with the codec layer. If the driver gets removed during the operation, you have to cancel the operation and sync with it in a proper way, then proceed the rest of the remove, not only a codec-specific resource management.
(snip)
Here I mentioned the codec driver, but it's applied to each lower-level component. It'd need some graceful way to communicate with the top-level card to assure the removal of the component.
I agree. I can't access to source code now (I'm in business-trip), but my head-acke is that kernel doesn't check return value from .remove when unbind case. Thus, we can't "cancel" remove operation. I'm happy if you can confirm it.