On Tue, 17 Sept 2024 at 11:50, Erez Geva <erezgeva@xxxxxxxxxx> wrote: > > From: Erez Geva <ErezGeva2@xxxxxxxxx> > > 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@xxxxxxxxx> > --- > .../bindings/mtd/jedec,spi-nor.yaml | 37 +++++++++++++++++++ > 1 file changed, 37 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml b/Documentation/devicetree/bindings/mtd/jedec,spi-nor.yaml > index 6e3afb42926e..d502b7fab2ce 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. > > + opt_n_regions: > + type: u32 > + 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 than 1 and mandatory for OTP. Sorry: "The value must be larger or equal to 1 and mandatory for OTP. " > + > + otp_len: > + type: u32 > + 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: > + type: u32 > + 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: > + type: u32 > + 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. > -- > 2.39.5 >
