diff options
| author | Konrad Dybcio <konrad.dybcio@linaro.org> | 2023-05-30 14:30:39 +0200 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@kernel.org> | 2023-08-10 07:58:34 +0200 |
| commit | 375b48f40fd03069658bb43bcd19a813f6dd8be5 (patch) | |
| tree | 27c4a1d99ea31fe5bd40c20c025fe79d3cf3df40 /tools/perf/scripts/python/stackcollapse.py | |
| parent | 9ac60db2bb4b9fb590abd05e6795d34df88e850c (diff) | |
media: venus: firmware: Leave a clue about obtaining CP VARs
The qcom_scm_mem_protect_video_var accepts two sets of <addr size>
pairs as arguments. They describe the virtual address ranges of the
CP (Content Protection) and CP_NONPIXEL regions. It is however not
immediately obvious how to obtain these values.
Leave a comment explaining how one can translate the vendor device
tree properties for use with the mainline driver.
Reviewed-by: Dikshita Agarwal <quic_dikshita@quicinc.com>
Reviewed-by: Vikash Garodia <quic_vgarodia@quicinc.com>
Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Signed-off-by: Stanimir Varbanov <stanimir.k.varbanov@gmail.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions