![](https://secure.gravatar.com/avatar/d930951cb00393ecf9c3db3a56d78fa9.jpg?s=120&d=mm&r=g)
8 Oct
2013
8 Oct
'13
11:34 a.m.
On Tue, Oct 08, 2013 at 10:29:33AM +0200, Markus Pargmann wrote:
To make proper error handling and only STOP functions that successfully started, we have to store the state of each function. The command error handling is done in pcm_native.c so we don't have any influence on that.
I meant just unwinding the things done in the trigger call.
Another possibility is to explicitly allow multiple _STOPs. Then I could fix the driver to store the clock state. But I would prefer a generic solution.
You're going to have to handle this anyway to be robust - what happens if it's the clock enable that fails?