SHM bridge creation is required to enable memory protection for both
remoteproc metadata and its memory region on Qualcomm SoCs like Glymur
running non-Gunyah based Hypervisors, unlike Kaanapali.
Having Glymur fall back to the Kaanapali binding is therefore incorrect
and breaks subsystem restart on Glymur.
Fix this by decoupling Glymur SoCCP PAS from Kaanapali and registering
it as its own binding.
Fixes: 8b54bacadc0c ("dt-bindings: remoteproc: qcom: Document pas for SoCCP on
Kaanapali and Glymur platforms")
Signed-off-by: Ananthu C V <[email protected]>
---
.../devicetree/bindings/remoteproc/qcom,kaanapali-soccp-pas.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/Documentation/devicetree/bindings/remoteproc/qcom,kaanapali-soccp-pas.yaml
b/Documentation/devicetree/bindings/remoteproc/qcom,kaanapali-soccp-pas.yaml
index 8fd6913e414d..e6c78d621d17 100644
--- a/Documentation/devicetree/bindings/remoteproc/qcom,kaanapali-soccp-pas.yaml
+++ b/Documentation/devicetree/bindings/remoteproc/qcom,kaanapali-soccp-pas.yaml
@@ -20,11 +20,11 @@ properties:
oneOf:
- items:
- enum:
- - qcom,glymur-soccp-pas
- qcom,hawi-soccp-pas
- qcom,maili-soccp-pas
- const: qcom,kaanapali-soccp-pas
- enum:
+ - qcom,glymur-soccp-pas
- qcom,kaanapali-soccp-pas
reg:
--
2.43.0
