[DOCS] ARM CPU plugin docs #10885
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,91 @@ | ||
| # Arm® CPU device {#openvino_docs_OV_UG_supported_plugins_ARM_CPU} | ||
|
|
||
|
|
||
| ## Introducing the Arm® CPU Plugin | ||
| The Arm® CPU plugin is developed in order to enable deep neural networks inference on Arm® CPU, using [Compute Library](https://github.com/ARM-software/ComputeLibrary) as a backend. | ||
|
|
||
| > **NOTE**: Note that this is a community-level add-on to OpenVINO™. Intel® welcomes community participation in the OpenVINO™ ecosystem and technical questions on community forums as well as code contributions are welcome. However, this component has not undergone full release validation or qualification from Intel®, and no official support is offered. | ||
|
|
||
| The Arm® CPU plugin is not a part of the Intel® Distribution of OpenVINO™ toolkit and is not distributed in pre-built form. To use the plugin, it should be built from source code. Plugin build procedure is described on page [How to build Arm® CPU plugin](https://github.com/openvinotoolkit/openvino_contrib/wiki/How-to-build-ARM-CPU-plugin). | ||
|
|
||
| The set of supported layers is defined on [Operation set specification](https://github.com/openvinotoolkit/openvino_contrib/wiki/ARM-plugin-operation-set-specification). | ||
|
|
||
|
|
||
| ## Supported inference data types | ||
| The Arm® CPU plugin supports the following data types as inference precision of internal primitives: | ||
|
|
||
| - Floating-point data types: | ||
| - f32 | ||
| - f16 | ||
| - Quantized data types: | ||
| - i8 | ||
|
|
||
|
|
||
| > **NOTE**: i8 support is experimental. | ||
|
|
||
| [Hello Query Device C++ Sample](../../../samples/cpp/hello_query_device/README.md) can be used to print out supported data types for all detected devices. | ||
|
|
||
| ## Supported features | ||
|
|
||
| ### Preprocessing acceleration | ||
| The Arm® CPU plugin supports the following accelerated preprocessing operations: | ||
| - Precision conversion: | ||
| - u8 -> u16, s16, s32 | ||
| - u16 -> u8, u32 | ||
| - s16 -> u8, s32 | ||
| - f16 -> f32 | ||
| - Transposion of tensors with dims < 5 | ||
| - Interpolation of 4D tensors with no padding (`pads_begin` and `pads_end` equal 0). | ||
|
|
||
| The Arm® CPU plugin supports the following preprocessing operations, however they are not accelerated: | ||
| - Precision conversion that are not mentioned above | ||
| - Color conversion: | ||
| - NV12 to RGB | ||
| - NV12 to BGR | ||
| - i420 to RGB | ||
| - i420 to BGR | ||
|
|
||
| See [preprocessing API guide](../preprocessing_overview.md) for more details. | ||
|
|
||
| ## Supported properties | ||
| The plugin supports the properties listed below. | ||
|
|
||
| ### Read-write properties | ||
| All parameters must be set before calling `ov::Core::compile_model()` in order to take effect or passed as additional argument to `ov::Core::compile_model()` | ||
|
|
||
| - ov::enable_profiling | ||
|
There was a problem hiding this comment. I suppose you also support streams, pinning, etc There was a problem hiding this comment. Thus these options are in the supported list they do not provide expected threading control. We even test only in latency (sync) mode only. I am going to enable tbb threading backend and provide full threading control as in the CPU plugin. It won't give any valuable throughput gain but give full threading control. So we can claim support of these options. |
||
|
|
||
| ### Read-only properties | ||
| - ov::supported_properties | ||
| - ov::available_devices | ||
| - ov::range_for_async_infer_requests | ||
| - ov::range_for_streams | ||
| - ov::device::full_name | ||
| - ov::device::capabilities | ||
|
|
||
|
|
||
| ## Known Layers Limitation | ||
| * `AvgPool` layer is supported via arm_compute library for 4D input tensor and via reference implementation for another cases. | ||
| * `BatchToSpace` layer is supported 4D tensors only and constant nodes: `block_shape` with `N` = 1 and `C`= 1, `crops_begin` with zero values and `crops_end` with zero values. | ||
| * `ConvertLike` layer is supported configuration like `Convert`. | ||
| * `DepthToSpace` layer is supported 4D tensors only and for `BLOCKS_FIRST` of `mode` attribute. | ||
| * `Equal` does not support `broadcast` for inputs. | ||
| * `Gather` layer is supported constant scalar or 1D indices axes only. Layer is supported as via arm_compute library for non negative indices and via reference implementation otherwise. | ||
| * `Less` does not support `broadcast` for inputs. | ||
| * `LessEqual` does not support `broadcast` for inputs. | ||
| * `LRN` layer is supported `axes = {1}` or `axes = {2, 3}` only. | ||
| * `MaxPool-1` layer is supported via arm_compute library for 4D input tensor and via reference implementation for another cases. | ||
| * `Mod` layer is supported for f32 only. | ||
| * `MVN` layer is supported via arm_compute library for 2D inputs and `false` value of `normalize_variance` and `false` value of `across_channels`, for another cases layer is implemented via runtime reference. | ||
| * `Normalize` layer is supported via arm_compute library with `MAX` value of `eps_mode` and `axes = {2 | 3}`, and for `ADD` value of `eps_mode` layer uses `DecomposeNormalizeL2Add`, for another cases layer is implemented via runtime reference. | ||
| * `NotEqual` does not support `broadcast` for inputs. | ||
| * `Pad` layer works with `pad_mode = {REFLECT | CONSTANT | SYMMETRIC}` parameters only. | ||
| * `Round` layer is supported via arm_compute library with `RoundMode::HALF_AWAY_FROM_ZERO` value of `mode`, for another cases layer is implemented via runtime reference. | ||
| * `SpaceToBatch` layer is supported 4D tensors only and constant nodes: `shapes`, `pads_begin` or `pads_end` with zero paddings for batch or channels and one values `shapes` for batch and channels. | ||
| * `SpaceToDepth` layer is supported 4D tensors only and for `BLOCKS_FIRST` of `mode` attribute. | ||
| * `StridedSlice` layer is supported via arm_compute library for tensors with dims < 5 and zero values of `ellipsis_mask` or zero values of `new_axis_mask` and `shrink_axis_mask`, for another cases layer is implemented via runtime reference. | ||
| * `FakeQuantize` layer is supported via arm_compute library in Low Precision evaluation mode for suitable models and via runtime reference otherwise. | ||
|
|
||
| ## See Also | ||
| * [How to run YOLOv4 model inference using OpenVINO™ and OpenCV on Arm®](https://opencv.org/how-to-run-yolov4-using-openvino-and-opencv-on-arm/) | ||
| * [Face recognition on Android™ using OpenVINO™ toolkit with Arm® plugin](https://opencv.org/face-recognition-on-android-using-openvino-toolkit-with-arm-plugin/) | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
F32 as it is used below in this form.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I set f32 everywhere