| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
This fixes the smatch warning below:
drivers/soc/qcom/memshare/msm_memshare.c:570 handle_alloc_generic_req()
warn: inconsistent returns 'mutex:&memsh_drv->mem_share'.
Bug: 35898203
Change-Id: I86f3d77c9bb471b1bc26360e11e378fa3d1a3f66
Signed-off-by: David Lin <dtwlin@google.com>
|
| |
|
|
|
|
|
|
| |
The patch adds an additional check to not free the clients memory
if the client has a designated property of allocate-on-request.
Change-Id: Iecf5886034ccd052ab82fff18cc66f1868604284
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
|
| |
|
|
|
|
|
|
|
|
| |
The patch performs Hypervisor mapping for guaranteed memshare
client's alloted memory at boot time and prevent allocation
for clients with size zero.
CRs-Fixed: 2062478
Change-Id: I96cc7b2014693d97f11411a7b62d2c365f21caf1
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
|
| |
|
|
|
|
|
|
|
| |
The patch updates the client's free memory
count variable after the successful allocation.
CRs-Fixed: 2046258
Change-Id: Ibae317596557e23d2b2278daf433bd293a8bd0be
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Currently, TZ is performing merging of resource groups
due to which NOC error is happening during access of
memory allocated to diag. This patch fixes the issue
by adding guard bytes so that merging of resource
groups will not happen.
CRs-Fixed: 2026525
Change-Id: I9829e5a07aef723c4261aa16dd5274cfeb1a75a3
Signed-off-by: Mohit Aggarwal <maggarwa@codeaurora.org>
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
The MSA0 memory that is re-assigned back to host need to have RWX
permissions for it to be used as data as well as instructions.
CRs-Fixed: 1116100
Change-Id: I7f3984c9285f1b2658c6f0f30e74397fbc0c3427
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
|
| |/
|
|
|
|
|
|
|
|
| |
This patch defines condition for collecting ramdump
only when ramdump collection is enabled, modem is crashed
and memshare is notified of SUBSYS_RAMDUMP_NOTIFICATION.
CRs-Fixed: 1114015
Change-Id: I7e3ca0794980fd21cc0a5d890df4aeadfd5fbbbb
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch frees up the dynamically allotted memory
when met with error condition and function return.
CRs-Fixed: 1106180
Change-Id: I01446fbdbb422dcb025ee50929b32f40a5a78681
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
Currently the XPU lock on memory allocated for memshare clients may not be
unlocked by MBA during SUBSYS_RAMDUMP_NOTIFICATION event and can result in
XPU violation while collecting ramdump.
This patch collects the ramdump on listening to SUBSYS_BEFORE_POWERUP
event.
CRs-Fixed: 1099029
Change-Id: I51732d5adc60ad106a44ba554818c18947e2e803
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
|
| |
|
|
|
|
|
|
|
|
| |
The ramdump driver uses the device pointer during ramdump read.
This change passes in the device pointer for memshare during
ramdump create and moves the call to the probe function.
CRs-Fixed: 1079523
Change-Id: I687696dbedfa0ce7e6053d70291a7beb6f81f82e
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Currently, on modem subsystem restart the area allocated from
HLOS to modem at runtime is not captured as part of the ramdump
collection.This patch creates separate elf files for all the
clients which are using memshare feature for memory allocation
which are later used to load as dumps.
CRs-Fixed: 1058744
Change-Id: I66436b7c2d9e02658cfc4c195ca78852b09c01f7
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
|
| |
|
|
|
|
|
|
|
|
| |
Currently, on Modem SSR, memshare driver receives notification
in which it free up the allocated memory. Due to timing issue,
free is happening after allocation. This patch synchronize
these operations.
Change-Id: I464d3b82f33ccdfd0988ef33fec8414d4ab4a550
Signed-off-by: Mohit Aggarwal <maggarwa@codeaurora.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This patch adds support for the hyp call to set up permissions
for the memory allocated for the modem clients.
This patch also identifies the debug messages with memshare
driver.
CRs-Fixed: 970173
Change-Id: I862a3c21eb4f791d5c7d93d4fb523bf8714c20cb
Signed-off-by: Katish Paran <kparan@codeaurora.org>
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
Currently, memshare relies on the system monitor only for
releasing memory for the allocated clients. It may happen that
XPU is still intact on the modem side while driver tries to
release the memory. This patch ensures that memory release only
happens if XPU is released.
Change-Id: I45716c0abe6bc08559854782ff73a332e148a7cb
Signed-off-by: Katish Paran <kparan@codeaurora.org>
|
|
|
Port the memshare driver and apply the following memshare driver
changes taken from msm-3.10 kernel branch as of msm-3.10 commit
4493220f memshare: Boot time allocation and handling
multiple clients
2ae4997a memshare: Donot re-allocate the memory for the
clients
059dcd59 memshare: Do not overwrite the response for the
failure case
ed6d183f memshare: Change the compatible property field
for child node
b473fc4e2 memshare: Free the memory after XPU unlocking is
done
95c114c39 memshare: Add query size api support for clients
60f310d4e memshare: Change dma attribute to
DMA_ATTR_NO_KERNEL_MAPPING
73075545 memshare: Remove local connection status variable
98dd2908 memshare: Place error check to prevent out of
bound access
Change-Id: Iecf0a9828efd1d56c309a2af882c13ce36e7fc06
Signed-off-by: Katish Paran <kparan@codeaurora.org>
Signed-off-by: Mohit Aggarwal <maggarwa@codeaurora.org>
|
