Lines Matching refs:driver

36  * This interface represents a device driver.
40      * Gets the capabilities of a driver.
44      *                - DEVICE_UNAVAILABLE if driver is offline or busy
46      * @return capabilities Capabilities of the driver.
54      * subgraph are fully supported by the vendor driver. If an operation may
59      * operations may only be fully supported if the vendor driver fully
63      *     are to be verified by the driver.
66      *     - DEVICE_UNAVAILABLE if driver is offline or busy
87      * Optionally, caching information may be provided for the driver to save
90      * types of cache file handles provided to the driver: model cache and data
96      * any offset. The driver must truncate a file to zero size before writing
98      * asynchronous preparation has finished. The driver must dup a file
135      * Optionally, the driver may save the prepared model to cache during the
138      * related to the cache may be invalid, or the driver may fail to save to
140      * driver may choose not to save to cache even if the caching information is
145      * such, some driver services may return partially prepared models, where
179      *     collision for a particular application. The driver cannot detect a
191      *     - DEVICE_UNAVAILABLE if driver is offline or busy
197      *     - RESOURCE_EXHAUSTED_* if the task was aborted by the driver
211      * two types of cache file handles provided to the driver: model cache
217      * driver must truncate a file to zero size before writing to that file. The file
219      * finished. The driver must dup a file descriptor if it wants to get access to
225      * cache has not been modified since it was last written by the driver.
256      * such, some driver services may return partially prepared models, where
276      *     to have a low rate of collision for a particular application. The driver
286      *     - DEVICE_UNAVAILABLE if driver is offline or busy
292      *     - RESOURCE_EXHAUSTED_* if the task was aborted by the driver
301      * Allocates a driver-managed buffer with the properties specified by the buffer descriptor
305      * certain role or property is not supported by the driver, the allocate
320      * or rank of the buffer may be unknown at this stage. As such, some driver services may only
326      * The driver must apply proper validatation upon every usage of the buffer, and must fail the
341      *     - DEVICE_UNAVAILABLE if driver is offline or busy
350      *     currently alive in the same driver service. If the buffer was unable to be allocated