Some platforms have laxed requirements on the placement of the rmtfs
memory region, introduce support for guard pages to allow the DeviceTree
author to rely on the OS/Linux for placement of the region.
Changes since v2:
- Rewrote DeviceTree binding description, to avoid dictating the OS
behavior.
- Adjusted addr and size before memremap(), to avoid mapping the guard
pages, and unnecessarily have to adjust the base pointer.
Changes since v1:
- Drop qcom,alloc-size in favour of using reserved-memory/size
- Introduce explicit property to signal that guard pages should be
carved out from this region (rather than always do it in the dynamic
case).
- Drop the dma_alloc_coherent() based approach and just add support for
the guard pages.
- Added handling of failed reserved-memory allocation (patch 3)
---
Bjorn Andersson (3):
dt-bindings: reserved-memory: rmtfs: Allow guard pages
soc: qcom: rmtfs: Support discarding guard pages
soc: qcom: rtmfs: Handle reserved-memory allocation issues
.../devicetree/bindings/reserved-memory/qcom,rmtfs-mem.yaml | 11 +++++++++++
drivers/soc/qcom/rmtfs_mem.c | 11 ++++++++++-
2 files changed, 21 insertions(+), 1 deletion(-)
---
base-commit: 926f75c8a5ab70567eb4c2d82fbc96963313e564
change-id: 20230920-rmtfs-mem-guard-pages-d3d0ed0cb036
Best regards,
--
Bjorn Andersson <quic_bjorande@quicinc.com>