Compile compat_qseecom_ioctl only if
CONFIG_COMPAT is enabled.
Change-Id: I334b0bccdaa30815ea17becdc086aa590d517f75
Signed-off-by: Anmolpreet Kaur <anmolpre@codeaurora.org>
If unload app was failed due to EBUSY, qseecom will not free
app list entry, but just restore app ref_cnt and return EBUSY
to client.
Change-Id: If7b20b52690a34ba9cf1b3c3e96f84583d221dec
Signed-off-by: Zhen Kong <zkong@codeaurora.org>
When unload app fails, return the correct return
value that we get from TZ and not translate it to
EFAULT. This will make sure that proper handling is
done at the calling side.
Change-Id: Ie850967e5c44b502b888324291a878d0a467b46b
Signed-off-by: Anmolpreet Kaur <anmolpre@codeaurora.org>
Fixes in qseecom driver to support shmbridge and
change parameters as hypervisor expects them to
be.
Change-Id: I57dc5d6fe7b74b45da2dee6de32c1251d77275ee
Signed-off-by: Anmolpreet Kaur <anmolpre@codeaurora.org>
Pass proper device node pointer to
of_reserved_mem_device_init_by_idx so that
it contains the of_node data which is needed
by the api.
Change-Id: I327f95657628eaa2e0e4bf98a919e003cdae7a86
Signed-off-by: Anmolpreet Kaur <anmolpre@codeaurora.org>
dma-buf destructor support is useful as it allows clients an opportunity
to undo any attributes, such as security attributes, they have applied to
the dma-buf's memory.
The destructor is called when the dma-buf is freed, if the destructor
returns an error the dma-buf's exporter release function is not called in
order to ensure that memory which has not been properly cleaned up isn't
returned to the system.
Change-Id: If2173b23b441157b3638110f02e2ff90ab6ad1aa
Signed-off-by: Liam Mark <lmark@codeaurora.org>
Signed-off-by: Swathi Sridhar <swatsrid@codeaurora.org>
[isaacm@codeaurora.org: resolve merge conflicts/qseecom redefinitions]
Signed-off-by: Isaac J. Manjarres <isaacm@codeaurora.org>
Add check to verify whether memory is allocated properly or not
and return error if its failed to allocate coherent buffer.
Change-Id: I234a637d20228d047f6fc11d374b6f13f28fed03
Signed-off-by: Gaurav Kashyap <gaurkash@codeaurora.org>
Signed-off-by: AnilKumar Chimata <anilc@codeaurora.org>
Copy the entire userspace request buffer to local kernel
buffer and use that to send to TZ. Update the response
received in the local buffer to the actual userspace buffer
after the request is complete.
Change-Id: I673d74a32966816c5248778fc967eb91da5b6df5
Signed-off-by: Anmolpreet Kaur <anmolpre@codeaurora.org>
Support for dma_buf_kmap() in ION on msm-5.4 will
be removed soon. It will support dma_buf_vmap() in
lieu of dma_buf_kmap(). Making changes for the same
in qseecom driver.
Change-Id: I4c2d6aaef58b41975279a01181c99cdeb18fb769
Signed-off-by: Anmolpreet Kaur <anmolpre@codeaurora.org>
add operation to deal with smcinvoke callback request
Change-Id: Ia79b380691dbda4298cdf088fe1a09280767ef17
Signed-off-by: Zhen Kong <zkong@codeaurora.org>
Set max size of dma segment to support requests of larger sizes.
Change-Id: I131a36bfc828d80c26bd5f463133edec6707c7fd
Signed-off-by: Prerna Kalla <prernak@codeaurora.org>
Listener operation switches the context between secure and
non-secure world while user requested qseecom operation is
put to wait. Between lisetner operation start and finish CPU
can do a speculative data fetch before secure world updates
the physical memory of user requested response data buffer which
was waiting in qseecom for listener operation to complete. This
speculative fetch will pull old data from RAM to cache and user
will end up reading stale data. Fix this by invalidating the
response data dma buffer after listener call completes. Also remove the
invalidate call for listener dma after scm call as data will not
be accessed in kernel after scm call is completed.
Change-Id: I68730a17b515f07a71a040a534f97ce97c65026c
Signed-off-by: Neeraj Soni <neersoni@codeaurora.org>
After unmapping the dmabuf, the pointers for dmabuf
and sg lists should be explicitly made NULL. This
change takes care of releasing the already unmapped
dma buf pointers and sg pointers.
Change-Id: Ia33231af761eddbdd6f71fda2c16b37289724b2e
Signed-off-by: Anmolpreet Kaur <anmolpre@codeaurora.org>
change qseecom_process_listener_from_smcinvoke parameters to work
with smcinvoke and upstream scm driver.
Change-Id: Ib5c12f731a4b8f3fba44b3bf8818da023080d708
Signed-off-by: Zhen Kong <zkong@codeaurora.org>
add compat_qseecom to support 32bit process to call ioctl on a
64-bit system.
Change-Id: I7e9b1c3d0cc34e3794265aa21db69e346f40833c
Signed-off-by: Zhen Kong <zkong@codeaurora.org>
As cma_get_base and cma_get_size are not intended to be used by
leaf drivers on GKI enabled build, use of_reserved_mem_lookup to
get heap base and size.
Change-Id: I91194187c89ff8c7f7d445833afce1a4716f0ea4
Signed-off-by: Zhen Kong <zkong@codeaurora.org>
When building as a module, the __setup() macro is undefined and the
compiler will warn about the now unused setup function. Mark it as
__maybe_unused to avoid the compiler warning.
Change-Id: Ic0dedbad341aae7d83169517d94af3b0ea038ac9
Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
Signed-off-by: Zhen Kong <zkong@codeaurora.org>
SCM driver has changed its interfaces. This requires corresponding
change in qseecom driver.
Change-Id: I9e55ed1bbbe04d25679f2e90d80e5913581887de
Signed-off-by: Dinesh K Garg <dineshg@codeaurora.org>
Add snapshot for qseecom driver from msm-4.19 commit 87a248d5b496d
("qseecom: invalidate listener buffer cache when get listener request").
Change-Id: I22261ad22fa8302b72b5569c68b311ca7fef9192
Signed-off-by: Zhen Kong <zkong@codeaurora.org>
