From 95022ca5c30571d46355d7fc538c472343517107 Mon Sep 17 00:00:00 2001 From: David Collins Date: Wed, 2 Feb 2022 17:53:13 -0800 Subject: [PATCH] dt-bindings: soc: qcom: pmic-pon-log: define bindings for multiple nvmem On some PMICs, the PON log is split between multiple NVMEM devices to allow for more entries. Define bindings so that multiple NVMEM devices can be specified to support this situation. Change-Id: Iead92ebd51473370fb5205e3fe9fe1a3a50eeb07 --- bindings/soc/qcom/qcom,pmic-pon-log.txt | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/bindings/soc/qcom/qcom,pmic-pon-log.txt b/bindings/soc/qcom/qcom,pmic-pon-log.txt index 1a906f39..4bfc320d 100644 --- a/bindings/soc/qcom/qcom,pmic-pon-log.txt +++ b/bindings/soc/qcom/qcom,pmic-pon-log.txt @@ -12,12 +12,14 @@ PON Log device accesses this log and parses it into a human readable format. - nvmem: Usage: required Value type: - Definition: phandle of the PMIC nvmem device containing the PON log + Definition: phandle list of the PMIC nvmem devices containing the PON + log. - nvmem-names: Usage: required Value type: - Definition: must be "pon_log" + Definition: must be "pon_log" if using a single nvmem device or + "pon_log0", "pon_log1", etc if using multiple nvmem devices. - qcom,pmic-fault-panic: Usage: optional @@ -26,10 +28,16 @@ PON Log device accesses this log and parses it into a human readable format. controlled panic shutdown if the preceding restart was caused by a PMIC fault. -Example: +Examples: pmic-pon-log { compatible = "qcom,pmic-pon-log"; nvmem = <&pmk8350_sdam_5>; nvmem-names = "pon_log"; }; + +pmic-pon-log { + compatible = "qcom,pmic-pon-log"; + nvmem = <&pmk8550_sdam_5>, <&pmk8550_sdam_6>; + nvmem-names = "pon_log0", "pon_log1"; +};