CameraDriver structure initialized explicitly to get version info
and remove INT32_C undefined macro definition to avoid compilation error.
Change-Id: If79a83383634fb379d860746ea3611e46295cd64
Signed-off-by: Ravi Kumar Bokka <quic_c_rbokka@quicinc.com>
Added a new API dynamicConfigureFDPort to allow secure/non-secure
FD port configuration from camera kernel.
Change-Id: I928d260249ef7bb10c43c125b5bc1c48379d89d4
Signed-off-by: Rajat Singh Deepak <quic_rajatsin@quicinc.com>
Expand SMCInvoke API to support possible
future requirements.
Change-Id: I9f6031751489c43a27afc2860a1cb9f87c7ebb87
Signed-off-by: Reut Zysman <quic_rzysman@quicinc.com>
Move the securemsm-kernel uapi headers to a uapi include path,
to conform with the uapi requirements.
NOTE: Duplicating qcedev.h & smcinvoke.h temporarily until
clients that manually include the path use the exported headers.
Change-Id: I33d390954ff0e6c721a5fa8256b431020e4f8912
Signed-off-by: Gaurav Kashyap <quic_gaurkash@quicinc.com>
This change makes changes to smcinvoke driver to handle suspend and resume
scenarios. If the accept thread gets interrupted, do not set the server state
as defunct if the thread is in freezing state, i.e. if the thread is going in
suspend. In such cases, increase timeout of that server so that invoke thread
waits indefinitely for response from userspace until the system resumes back.
Tests:
1. Stability testing has been done on kalama.
2. smcinvoke vendor client testing is done on pineapple.
Change-Id: Iaa7b91d6ed484305349c04468263919e26a3316d
Signed-off-by: Anmolpreet Kaur <quic_anmolpre@quicinc.com>
Change consists creation of ADCI thread at SMCInvoke
driver initialization
Change consists creation of ADCI thread at SMCInvoke driver initialization
Following scenario have been tested for this change
(1) ADCI thread creation and QTEE invocation during driver initialization
(2) Backward Compatibility - IF ADCI feature is not supported (OBJECT_ERROR_INVALID)
then exit the ADCI thread gracefully after cleaning up all the resources
(3) Leak Test: All the resources held by ADCI thread should be released if ADCI feature
is not supported by QTEE
(i) adci task_struct state and exit state:
state = TASK_RUNNING , exit_state = 0 (While ADCI thread execution)
state = TASK_DEAD , exit_state = EXIT_DEAD (During ADCI thread termination)
(ii) adci task_struct = NULL (fetched based on adci thread_id) which make sure
task_struct has been deallocated
(4) SMCInvoke related Test: All the internal(suuported),memobj and cbo testing has been performed.
Change-Id: I2916ce260fae293b88fbc8b9d24baccdee1ea89f
Signed-off-by: Pawan Rai <quic_pawarai@quicinc.com>
We are exposing headers present in "include/linux" for the rest of the kernel DLKM's.
Aallow other kernel teams to access these headers.
Change-Id: I19c5591d885c7042ba3acd312ce9cb2bddc995c9
CRS-Fixed: 3338788
This reverts commit 796ae71391.
This commit is being reverted due to build conflicts
with other teams
CRS-Fixed: 3354563
Change-Id: I915cc5bd0e718a1b82641ac02d2f0184f2fa1f37
We are exposing headers present in "include/linux" for the rest of the kernel DLKM's.
These changes allow for other kernel teams to access these headers.
CRS-Fixed: 3338788
Change-Id: I5926ddeee8541398b32010db0b01af529b19fa3e
expose ITrustedCameraDriver header file to camera so that
camera kernel driver can trigger protect/unprotect call.
CRS-Fixed: 3343680
Change-Id: I011f17a93f9d7c32140835406488def34429f983
