Skip to content

QCLINUX: firmware: qcom: memory_dump_v2: assign dump table region to non-secure world - #1712

Open
Jie Gan (jiegan0107) wants to merge 1 commit into
qualcomm-linux:tech/noup/debug/allfrom
jiegan0107:tech/noup/debug/all
Open

QCLINUX: firmware: qcom: memory_dump_v2: assign dump table region to non-secure world#1712
Jie Gan (jiegan0107) wants to merge 1 commit into
qualcomm-linux:tech/noup/debug/allfrom
jiegan0107:tech/noup/debug/all

Conversation

@jiegan0107

Copy link
Copy Markdown

Add assign_dump_table_region() to notify TZ that the memory dump table region should be made accessible to AOP, via a self-contained SCM SMC call (QCOM_SCM_SVC_UTIL / QCOM_SCM_UTIL_DUMP_TABLE_ASSIGN). The SMC convention probe (__get_convention()) and dispatch helper are kept local to this driver rather than exported from qcom_scm, since only the register-argument SMC path is needed here.

Wire it into mem_dump_alloc(), falling back to the IMEM-based dump table registration path if the SCM call fails.

…non-secure world

Add assign_dump_table_region() to notify TZ that the memory dump table
region should be made accessible to AOP, via a self-contained SCM SMC
call (QCOM_SCM_SVC_UTIL / QCOM_SCM_UTIL_DUMP_TABLE_ASSIGN). The SMC
convention probe (__get_convention()) and dispatch helper are kept
local to this driver rather than exported from qcom_scm, since only
the register-argument SMC path is needed here.

Wire it into mem_dump_alloc(), falling back to the IMEM-based dump
table registration path if the SCM call fails.

signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant