[PATCH v5 3/5] dt-bindings: mtd: spi-nor: add OTP parameters

Erez Geva
2024-09-20T18:13:23Z

From: Erez Geva <ErezGeva2@gmail.com>

Some flash devices need OTP parameters in device tree.
As we can not deduce the parameters based on JEDEC ID or SFDP.

Signed-off-by: Erez Geva <ErezGeva2@gmail.com>
---
.../bindings/mtd/jedec,spi-nor.yaml | 39 +++++++++++++++++++
1 file changed, 39 insertions(+)

diff --git a/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml b/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml
index 6e3afb42926e..4f7bb3f41cb1 100644
--- a/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml
+++ b/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml
@@ -90,6 +90,43 @@ properties:
the SRWD bit while writing the status register. WP# signal hard strapped to GND
can be a valid use case.

+ otp-n-regions:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description:
+ Some flash devices need OTP parameters in the device tree.
+ As we can not deduce the parameters based on JEDEC ID or SFDP.
+ This parameter indicates the number of OTP regions.
+ The value must be larger or equal to 1 and mandatory for OTP.
+
+ otp-len:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description:
+ Some flash devices need OTP parameters in the device tree.
+ As we can not deduce the parameters based on JEDEC ID or SFDP.
+ This parameter indicates the size (length) in bytes of an OTP region.
+ Currently the driver supports symmetric OTP,
+ which means all regions must use the same size.
+ The value must be positive and mandatory for OTP.
+
+ otp-offset:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description:
+ Some flash devices need OTP parameters in the device tree.
+ As we can not deduce the parameters based on JEDEC ID or SFDP.
+ This parameter indicates the offset in bytes of
+ an OTP region relative to its previous.
+ User can omit it if the offset equals the length.
+ Or in case we have a single OTP region.
+
+ otp-base:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description:
+ Some flash devices need OTP parameters in the device tree.
+ As we can not deduce the parameters based on JEDEC ID or SFDP.
+ This parameter indicates the base in bytes of the first OTP region.
+ User can omit it if the base is zero.
+ I.e. the address of the first OTP region starts from 0.
+
reset-gpios:
description:
A GPIO line connected to the RESET (active low) signal of the device.
@@ -118,6 +155,8 @@ examples:
spi-max-frequency = <40000000>;
m25p,fast-read;
reset-gpios = <&gpio 12 GPIO_ACTIVE_LOW>;
+ otp-len = <512>;
+ otp-n-regions = <1>;
};
};
...
--
2.39.5