Task execution hardware, can be used in combination, for example: HB_UCP_DSP_CORE_0 | HB_UCP_GDC_CORE_0 represents that the current task can use either the DSP 0 core or the GDC 0 core, the scheduling is leftto the UCP's own decision based on the load.
HB_UCP_CORE_ANY must be used alone and cannot be ORed with other backends.
Member
| Member Name | Description |
|---|---|
HB_UCP_CORE_ANY | Arbitrary executable hardware on Soc. |
HB_UCP_BPU_CORE_0 | BPU core 0. |
HB_UCP_BPU_CORE_1 | BPU core 1. |
HB_UCP_BPU_CORE_2 | BPU core 2. |
HB_UCP_BPU_CORE_3 | BPU core 3. |
HB_UCP_BPU_CORE_ANY | Arbitrary BPU core. |
HB_UCP_DSP_CORE_0 | DSP core 0. |
HB_UCP_DSP_CORE_1 | DSP core 1. |
HB_UCP_DSP_CORE_ANY | Arbitrary DSP core. |
HB_UCP_GDC_CORE_0 | GDC core 0. |
HB_UCP_GDC_CORE_ANY | Arbitrary GDC core. |
HB_UCP_STITCH_CORE_0 | STITCH core 0. |
HB_UCP_LKOF_CORE_0 | LKOF core 0. |
HB_UCP_JPU_CORE_0 | JPU core 0. |
HB_UCP_JPU_CORE_1 | JPU core 1. |
HB_UCP_JPU_CORE_2 | JPU core 2. |
HB_UCP_JPU_CORE_ANY | Arbitrary JPU core. |
HB_UCP_VPU_CORE_0 | VPU core 0. |
HB_UCP_VPU_CORE_ANY | Arbitrary VPU core. |
HB_UCP_PYRAMID_CORE_0 | PYRAMID core 0. |
HB_UCP_PYRAMID_CORE_1 | PYRAMID core 1. |
HB_UCP_PYRAMID_CORE_2 | PYRAMID core 2. |
HB_UCP_PYRAMID_CORE_ANY | Arbitrary PYRAMID core. |
HB_UCP_ISP_CORE_0 | ISP core 0. |
HB_UCP_ISP_CORE_1 | ISP core 1. |
HB_UCP_ISP_CORE_ANY | Arbitrary ISP core. |