Lines Matching refs:extension

30 ## Vendor extension definition
32 The vendor creates and maintains a header file with the extension definition. A
33 complete example of an extension definition can be found in
36 Each extension must have a unique name that starts with the reverse domain name
39 Note: Names of extension operation and operand types must be qualified with a
82 An extension operation can use any operand type, including nonextension operand
84 another extension, the driver must support the other extension.
86 Extensions can also declare custom structures to accompany extension operands.
101 extension support. This section provides an overview of the C API.
103 To check whether a device supports an extension, use
111     // The device supports the extension.
116 To build a model with an extension operand, use `ANeuralNetworksModel_getExtensionOperandType`
133 to associate additional data with an extension operand.
144 To build a model with an extension operation, use
157 ## Adding extension support to an NNAPI driver
161 extension.
182 `ExtensionTypeEncoding::HIGH_BITS_PREFIX` bits is the extension
184 bits represents the type or operation of the extension.
186 When handling an operation or operand type, the driver must check the extension
187 prefix. If the extension prefix has a nonzero value, the operation or operand
188 type is an extension type. If the value is `0`, the operation or operand type
189 isn't an extension type.
191 To map the prefix to an extension name, look it up in `model.extensionNameToPrefix`.
192 The mapping from the prefix to the extension name is a one-to-one correspondence
194 same extension name in different models.
196 The driver must validate extension operations and data types because the NNAPI
197 runtime can't validate particular extension operations and data types.
199 Extension operands can have associated data in `operand.extraParams.extension`,