bae0381f76a3dbae0220798f15d21c1bc1b56e5b

The current secure camera implementation suffers with a few issues in terms of typecasting, error handling and in populating the information in the right data structures when the new SCM API is used on the targets without domain ID support. In addition, we needed to be explicit in failing to acquire if dual IFE is required in secure camera use cases as it is not a supported feature as of now. CRs-Fixed: 3317248 Change-Id: Idb762158b0ff0e0a0d6d51de4770fc3d9d9072c8 Signed-off-by: Vijay Kumar Tumati <quic_vtumati@quicinc.com>
Описание
No description provided
Languages
C
98.7%
C++
0.9%
Makefile
0.3%
Starlark
0.1%