Searched refs:executing (Results 1 – 15 of 15) sorted by relevance
1 // This example client is written as a test, but it is executing from a system
27 * sub-states: executing, tripped and error.
25 * sub-states: executing, tripped and error.
296 executing = false; in MockBufferSource()307 bool executing; member313 executing = true; in onOmxExecuting()335 executing = false; in onOmxIdle()346 EXPECT_EQ(executing, false); in onInputBufferAdded()
52 * Data structure passed to the driver for executing commands
67 * Data structure passed to the driver for executing commands
29 * state has three sub-states: executing, tripped and error.
33 * sub-states: executing, tripped and error.
466 * Prefer executing in a way that minimizes battery drain.
254 * callback should only be sent once the device has finished executing
952 * called with a bootloader-only key after the bootloader has finished executing, it must954 * the bootloader has finished executing is implementation-defined.
1798 * 1) Provides the input and output data to be used when executing the model.
5739 * 1) Provides the input and output data to be used when executing the model.