S100 OpenExplorer

# #hbUCPBackend

`#define HB_UCP_CORE_ANY (0 << 0) #define HB_UCP_BPU_CORE_0 (1ULL << 0) #define HB_UCP_BPU_CORE_1 (1ULL << 1) #define HB_UCP_BPU_CORE_2 (1ULL << 2) #define HB_UCP_BPU_CORE_3 (1ULL << 3) #define HB_UCP_BPU_CORE_ANY (1ULL << 7)`

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.

Attention

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.

On This Page