hi_mpi_isp_init
Applicability
|
Product |
Supported |
|---|---|
|
Atlas 350 Accelerator Card |
☓ |
|
|
☓ |
|
|
☓ |
|
|
√ |
|
|
☓ |
|
|
☓ |
Function Description
Initializes the ISP firmware.
Prototype
hi_s32 hi_mpi_isp_init(hi_vi_pipe vi_pipe)
Parameters
|
Parameter |
Input/Output |
Description |
|---|---|---|
|
vi_pipe |
Input |
VI pipe ID. Value range: [0, 12) |
Returns
- 0: success
- Other values: failure. For details, see ISP Return Codes.
Restrictions
- Before calling this API, you must call the hi_mpi_isp_set_pub_attr API to set the public image attributes.
- To ensure that resources are completely cleared before the previous process exits, you are advised to call hi_mpi_isp_exit and before calling this API to initialize the ISP firmware.
- Multi-process is not supported. This API must be called in the same process as the hi_mpi_isp_sensor_reg_callback, hi_mpi_isp_run, hi_mpi_isp_exit, hi_mpi_ae_register, and hi_mpi_awb_register APIs.
- This API cannot be called repeatedly.
- When the same VI pipe is used, multiple threads cannot be used to create and destroy the ISP (that is, multiple threads call the hi_mpi_isp_sensor_reg_callback, hi_mpi_isp_run, hi_mpi_isp_exit, hi_mpi_ae_register, and hi_mpi_awb_register APIs at the same time).
- After the ISP is initialized, it takes one frame for the hardware to read the algorithm coefficient table. Therefore, within one frame after this API is called, hi_mpi_vi_stop_pipe cannot be called to stop the VI pipe.
Parent topic: ISP System Control and 3A Algorithm Registration