| C_SW_001 |
To read the Camera software ICP output from the CPU, which is in
the form of an NvSciBufObj, the assumption is that
users flushed the buffer NvSciBufObj points to by
by calling NvSciBufObjFlushCpuCacheRange() before
reading the buffer from the CPU. |
| C_SW_002 |
Users should configure at least one ISP output to enable exposure
and white balance corrections. |
| C_SW_003 |
Users who implement their own auto control plugin must not invoke
Camera software APIs. |
| C_SW_004 |
To tailor the attributes, users should supply the values for
those attributes while retrieving. |
| C_SW_005 |
Users who implement their own auto control plugins must ensure
that the auto control processing occurs within the allocated
time. |
| C_SW_006 |
Users must register only one NvSciSyncObj for
ISP postfence and share the fence for all three ISP outputs. |
| C_SW_007 |
Users must not expect error notifications from a disabled link.
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 will
resume once the link is enabled. |