Application Guidelines#
Unique ID |
Desciption |
---|---|
C_SW_001 |
To read the Camera software ICP output from the CPU, which is in the form of an |
C_SW_002 |
Users need to configure at least one ISP output to enable exposure and white balance corrections. |
C_SW_003 |
Users who implement their own auto control plugin need to avoid invoking Camera software APIs. |
C_SW_004 |
To tailor the attributes, users need to supply the values for those attributes while retrieving. |
C_SW_005 |
Users who implement their own auto control plugins need to ensure that the auto control processing occurs within the allocated time. |
C_SW_006 |
Users need to register only one |
C_SW_007 |
Error notifications are paused when a link is disabled. When users disable a link to a camera module by using the Camera software APIs, Camera software will not receive error notifications from that Camera module. Camera module error notifications resume once the link is enabled. |
C_SW_008 |
Users need to register at least four capture buffers and three processing buffers per ISP output per camera pipeline to avoid frame drops. Note These numbers are recommended for one consumer. Increase the buffer count to accommodate more consumers. |
C_SW_009 |
As the initial images are processed using the settings from calibration data, they may not have optimal exposure and white balance. Users need to consider this while making safety critical decisions based on image characteristics. |
C_SW_010 |
Users need to limit the frequency of operations that access the I2C bus during runtime to prevent I2C bus saturation. |
C_SW_011 |
When setting a high number of |