diff options
author | Caleb Connolly <caleb@connolly.tech> | 2021-05-02 04:42:57 +0300 |
---|---|---|
committer | Bjorn Andersson <bjorn.andersson@linaro.org> | 2021-05-26 06:40:32 +0300 |
commit | e60fd5ac1f6851be5b2c042b39584bfcf8a66f57 (patch) | |
tree | 114184978c65fef28407c397af87f44956c800f1 /Documentation/driver-api/gpio | |
parent | 5eabd602d2ff5c9b3fbd250ab09e355336691d8e (diff) | |
download | linux-e60fd5ac1f6851be5b2c042b39584bfcf8a66f57.tar.xz |
arm64: dts: qcom: sdm845-oneplus-common: guard rmtfs-mem
The rmtfs_mem region is a weird one, downstream allocates it
dynamically, and supports a "qcom,guard-memory" property which when set
will reserve 4k above and below the rmtfs memory.
A common from qcom 4.9 kernel msm_sharedmem driver:
/*
* If guard_memory is set, then the shared memory region
* will be guarded by SZ_4K at the start and at the end.
* This is needed to overcome the XPU limitation on few
* MSM HW, so as to make this memory not contiguous with
* other allocations that may possibly happen from other
* clients in the system.
*/
When the kernel tries to touch memory that is too close the
rmtfs region it may cause an XPU violation. Such is the case on the
OnePlus 6 where random crashes would occur usually after boot.
Reserve 4k above and below the rmtfs_mem to avoid hitting these XPU
Violations.
This doesn't entirely solve the random crashes on the OnePlus 6/6T but
it does seem to prevent the ones which happen shortly after modem
bringup.
Fixes: 288ef8a42612 ("arm64: dts: sdm845: add oneplus6/6t devices")
Signed-off-by: Caleb Connolly <caleb@connolly.tech>
Link: https://lore.kernel.org/r/20210502014146.85642-4-caleb@connolly.tech
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Diffstat (limited to 'Documentation/driver-api/gpio')
0 files changed, 0 insertions, 0 deletions