Add changes to support compilation and enablement for
qtee modules on sun. These changes do not enable the
compilation but add a support to enable the driver
compilation just by setting ENABLE_SECUREMSM_QTEE_DLKM to true.
1. Flag ENABLE_SECUREMSM_QTEE_DLKM ensures that we can
enable compilation and enablement of smcinvoke,tzlog and qseecom
driver irrespective of high level KERNEL_DLKM* flags.
2. BUILD.bazel and build/sun.bzl changes to enable bazel
configurations for smcinvoke and tzlog driver once they are enabled
in Android.mk.
Change-Id: I5574c4b328266c3344aac435d034e6639a05fb12
Signed-off-by: Anmolpreet Kaur <quic_anmolpre@quicinc.com>
Module remove call is not cleaning up char dev completely.
Update remove call sequence to call class_destroy, device_destroy
and cdev_del to clean up char dev complexly.
Change-Id: I07f28c27ac0ca78cb8223118bd0be3b3a5654224
Signed-off-by: Om Prakash Singh <quic_omprsing@quicinc.com>
ion is deprecated now. Removing header as it is no longer
needed.
Test:
Tested compilation on sun and pineapple builds.
Change-Id: Ic67d389b7161e7c1daade147a719140456156ca3
Signed-off-by: Anmolpreet Kaur <quic_anmolpre@quicinc.com>
StsHostTestCases-android.security.sts.Poc16_11#testPocCVE_2016_6752 is
failed due to assertion error due to address pattern.
Change-Id: Id1bdf0637ac9ee1bc493e87147128153faaed546
Signed-off-by: kodanda rami reddy v <quic_kreddyv@quicinc.com>
Moving to a new kernel version has led to
enablement of new compiler warnings. These
issues came during compilation enablement
of securemsm modules for sun.
Change-Id: Id807a642b9465dda79680c28d4a6eeef64a45eba
Signed-off-by: Anmolpreet Kaur <quic_anmolpre@quicinc.com>
The clean command will clear the KERNEL_SRC path, then cause
securemsmdlkm compile fail.
Change-Id: I3b956f87b2d46d21399104796ac5f7d2a5521cbd
Signed-off-by: jianshu <quic_jianshu@quicinc.com>
Also reset the output buffer after processing.
Change-Id: Ib8d9b3ffe4c25c3c699df561d7f37776a8fcd538
Signed-off-by: Amirreza Zarrabi <quic_azarrabi@quicinc.com>
mem_buf_retrieve() is what will actually create a DMA-BUF, along with
the struct file that underpins the DMA-BUF's lifetime and user space
interface. The FD RWX permissions are set during this time, and
currently, we just supply a flags value of 0, corresponding to
read-only. Set the file permissions as O_RDWR accordingly.
Separately, dma_buf_fd(), which just exposes a DMA-BUF's struct file
to user space, ignores all other arguments other than O_CLOEXEC, so
discard the other arguments.
Change-Id: I5e81909f3b87edb28cbbb087ec1994004fd82e45
Signed-off-by: Chris Goldsworthy <quic_cgoldswo@quicinc.com>
Add framework for piggy back of mo at time of callback too.
TEST Cases:
1. Ran GP TEST cases with MO for 5 hours.
2. L0 testing done.
3. Added new test for same in tzecotest load app.
Change-Id: I4d0d0b30303264f105f976109d44ca03159b970c
Signed-off-by: Nitin LNU <quic_nlakra@quicinc.com>
For hdcp and smmu, include smcinvoke_object.h
instead of smcinvoke.h.
Change-Id: Ieab17cfe70b779bd19d7596a3057e6d6c530b997
Signed-off-by: Reut Zysman <quic_rzysman@quicinc.com>
cleanup qcedev_compat driver support that is not
needed on latest Qualcomm Technologies, Inc. plateforms.
Change-Id: Id61e06a5a3cc1b3e9474c328f26761ffda9a55e0
Signed-off-by: Udit Tiwari <quic_utiwari@quicinc.com>
This change is a correction on top of commit: b1c6f1e9
which provided the fix for same issue but had a catch.
In the previous change, kref_put was being done on an
empty list. This change fixes that issue and deletes the
list after kref_put is done.
Root cause of original issue:
If invoke call fails due to some reason, map objects created
for memory objects should also be released. Failing to do so,
creates a memory leak as TZ is unaware of these objects and
no one calls release on these.
Change-Id: Ibad583f6c45fbed05539757eb50a39289d532328
Signed-off-by: Anmolpreet Kaur <quic_anmolpre@quicinc.com>
Added check to prevent more than one listener registration
on a fd. This could lead to potential vulnerabilities of use
after free while unregistering the listener.
Change-Id: Ia2973853943b5619bcf2047629b9c193f6a8c5cf
Signed-off-by: Pawan Rai <quic_pawarai@quicinc.com>
1.Invalid shm handle release causing in to invalid address access.
so added check to release the handle only if it is valid.
2.Skip the error if hdcpsrm ta loading is failing with already
loaded error becase hdcpsrm can be loaded from wfd stack
also when external monior is connected with sink device.
Change-Id: Ic6c48eabfc383352e8de781bebbc2e6cd7e964e0
Signed-off-by: Sheik Anwar Shabic Y <quic_sheikanw@quicinc.com>
Change the location of our UAPI directory in order to satisfy
directory structure requirements.
Change-Id: I620f441833fc1cbe5cd871028f2babba47af5ef4
Signed-off-by: Chris Goldsworthy <quic_cgoldswo@quicinc.com>
Added reboot notifier function to do resource clean up during reboot
as mutliple issues during reboot were noticed where release call was
not invoked by OS for qseecom driver. This lead listener req to wait for
for response which hold reboot for infinite time.
Test Cases:
1. Ran HDCP_denit at reboot to check reboot stuck.
2. Mutliple Reboots.
Change-Id: I7917cf9a89feca731e479538e7f4fa0671a29edd
Signed-off-by: Indranil Pradhan <quic_ipradhan@quicinc.com>
As per the current flow, tme_log dir is created by default for all type
of targets.
Below are the cases where tme_log should not be created:
- For non TME targets.
- Target support TME, but tmecrashdump-address-offset value is not
specified in DT.
- If DT value is provided, but faced an error in ioremapping passed
address value.
Alongwith tme_log, fix hyp/rm log node creation behavior as well by
extending this interface.
Change-Id: Ie26701d551aa48ff896642e04db2392860035e1e
Signed-off-by: Kuldeep Singh <quic_kuldsing@quicinc.com>
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>
Previously on sps_transfer failure, a fail message and descriptor
information would be logged. Changed to only log a fail message.
Descriptor can still be logged with QCE_DEBUG defined.
Change-Id: I3dfc2d0f58ea99302a62bf3aeeaa3d3e9f587b16
Signed-off-by: Daniel Perez-Zoghbi <quic_dperezzo@quicinc.com>
Add support for qcom,commonlib-loaded-by-hostvm
to use commonlib loaded by host VM.
Change-Id: I3a9f08bb53dde7545f518247ae885411ae8eef64
Signed-off-by: venkata sateesh <quic_vencher@quicinc.com>
Signed-off-by: Nishant Raj <quic_nishraj@quicinc.com>
Print the error log indicating that a mapping request
was received only in case the memory object async
support was enabled.
Change-Id: I1e02e4cb8501d539fdd6767152697a41033aa1d6
Signed-off-by: Reut Zysman <quic_rzysman@quicinc.com>
Guard enablement of QTEE drivers using a new QMAA flag
so that these driver can be enabled independently.
Change-Id: I8d78499a9ff66519afceb4e36f32737ed30584ed
Signed-off-by: Smita Ghosh <quic_smitag@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>
