[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220324042024.26813-4-peng.fan@oss.nxp.com>
Date: Thu, 24 Mar 2022 12:20:23 +0800
From: "Peng Fan (OSS)" <peng.fan@....nxp.com>
To: ulf.hansson@...aro.org, robh+dt@...nel.org, krzk+dt@...nel.org,
shawnguo@...nel.org, s.hauer@...gutronix.de, wg@...ndegger.com,
mkl@...gutronix.de, davem@...emloft.net, kuba@...nel.org,
pabeni@...hat.com, qiangqing.zhang@....com
Cc: kernel@...gutronix.de, festevam@...il.com, linux-imx@....com,
linux-mmc@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-can@...r.kernel.org, netdev@...r.kernel.org,
Peng Fan <peng.fan@....com>
Subject: [PATCH 3/4] dt-bindings: mmc: imx-esdhc: introduce nvmem property
From: Peng Fan <peng.fan@....com>
To i.MX8M Family variants, sdhc maybe fused out. Bootloader could use
this property to read out the fuse value and mark the node status
at runtime.
Signed-off-by: Peng Fan <peng.fan@....com>
---
Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml b/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml
index 7dbbcae9485c..67dfe6d168d0 100644
--- a/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml
+++ b/Documentation/devicetree/bindings/mmc/fsl-imx-esdhc.yaml
@@ -57,6 +57,15 @@ properties:
interrupts:
maxItems: 1
+ nvmem-cells:
+ maxItems: 1
+ description:
+ Nvmem data cell that indicate whether this IP is fused or not.
+
+ nvmem-cell-names:
+ items:
+ - const: fused
+
fsl,wp-controller:
description: |
boolean, if present, indicate to use controller internal write protection.
--
2.35.1
Powered by blists - more mailing lists