Issue:
qcedev_async_req status is updated after sending complete signal
that makes qcedev_ioctl exit and freed the memory.
Fix:
update qcedev_async_req status before sending complete signal.
Change-Id: I6c224b4775b8860c1c50f9a1f9e3705a6ca76e34
Signed-off-by: Om Prakash Singh <quic_omprsing@quicinc.com>
(cherry picked from commit 582cf8006a08f459573a30821270d72fd8788b15)
In an offload crypto operation there are some expected errors, e.g.
KeyPauseError. We have a shortened wait time to capture these errors,
however the current wait time of 20ms was too short and some valid
operations were timing out just before the request is completed, causing
a race condition. Here we change to 50ms as a normal operation should
not take this long. Calculated by 8 requests submitted * 4MB (max size)
at about 5Gbps processing rate. This is a conservative estimate.
Change-Id: I5bccd81ca3dda9d4fca1f302b7961dbdb22f9f58
Signed-off-by: Daniel Perez-Zoghbi <quic_dperezzo@quicinc.com>
In mem-map lock api its suppose to enter and exit with holding
lock but there is scenario where we are unlocking in locked API.
Change-Id: I79d8dc350df00d086c9d4d8a58a7b928734be598
Signed-off-by: Nitin LNU <quic_nlakra@quicinc.com>
(cherry picked from commit 657c43f2b767274f940efd66b6d685cf7a0c9884)
Resolve compilation issues related to printing
caused by kernel upgrade.
Change-Id: I34db6dab0af32b75d0877ae55e6a493004e11de9
Signed-off-by: songrui <quic_songrui@quicinc.com>
Resolve compilation issues related to printing caused by kernel upgrade
Change-Id: Iaf55c59e77c7f23581372db711debf6059c380dd
Signed-off-by: songrui <quic_songrui@quicinc.com>
HDCP has a dependency on Qseecomd for HDCP key
verification and other SCM calls. Qseecomd takes
a lot of time to be available during boot because
of which HDCP init fails.
Adding retry mechanism only when there is hdcp key
verification failure due to Qseecomd not starting
in time. For other error codes, like HDCP key not
programmed, there will be no retry.
If Qseecomd doesn’t come up within maximum retries,
code will stop retrying and hdcp key verification
will fail. For each retry, there is a sleep of 100ms.
The number of retries can be changed from the dtsi file.
By default, we are allowing 40 retries but it can be
changed. 40 retries are based on the qseecomd KPI which
can be anywhere between 2.9 sec to 3.6 sec.
Change-Id: I3661b349ec44604147d6e6700307fa416904bbfa
Signed-off-by: Shubham Dhiman <quic_shubhamd@quicinc.com>
Add flags for each feature and these flags to use
enable/disable features.
Enable SMCINVOKE driver and disable other drivers
on HGY platform.
Change-Id: I5eca4771aaa3001ecc0d8c06060c951923aa0619
Signed-off-by: Santosh Dronamraju <quic_sdronamr@quicinc.com>
Updating the hardcoded path to store into a variable to support
multiple vendor components in parallel for build compilations.
Tests:
Compilation validation and device is booting up successfully.
Change-Id: I6a058e538a5050066de0737b834ec182c1283fc3
Signed-off-by: Ananth Sadvi Bogavalli <quic_abogaval@quicinc.com>
In latest kernel upgrade Zero Length arrays are not allowed.
Replace with Flexible arrays.
Change-Id: Ide4ce5ac5f75197a432fb99333a702cdc4ff88c5
Signed-off-by: Anmolpreet Kaur <quic_anmolpre@quicinc.com>
Compile sec-module-symvers only if at least one of the
ENABLE_SECUREMSM_QTEE_DLKM or ENABLE_SECUREMSM_DLKM is true.
Change-Id: Ibf69d19ef311d02862f8a87dabd01875ae2cdcab
Signed-off-by: Anmolpreet Kaur <quic_anmolpre@quicinc.com>
kernel-qcom 6.1 has some changes in api definations
and header file locations. This change fixes compilation
errors related to those changes.
Change-Id: I6162ffe9e671a8e94d80e9ec01839566c617aa03
Signed-off-by: Anmolpreet Kaur <quic_anmolpre@quicinc.com>
Before initating the ioctl lets first check the state of qseecom
is yet ready or not.
Test:
1. L0 Validation
2. Introduced a sleep in init path and tested the qseecom node.
Change-Id: Ic93ab91a4281ff615b629fdeb936fcd924589b5d
Signed-off-by: Nitin LNU <quic_nlakra@quicinc.com>
dmabuf having the changes in 6.1 for clean and invalidate ,
made similar changes to do invalidation and clean in
qseecom corresponding to dmabuf changes.
Change-Id: I23a9686ce4902d86c8ef60c099fcc4394356e114
Signed-off-by: Nitin LNU <quic_nlakra@quicinc.com>
Change DMA HEAP CMO's clean and flush as per changes
for 6.1 kernel.
Change-Id: Ie36fc1efdeecd1ab1afd3d9a59372b762bb8ad0d
Signed-off-by: Nitin LNU <quic_nlakra@quicinc.com>
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>
