On 2022-08-25 at 16:13:29 +0200, Johannes Zink wrote: > This patch introduces additional memory areas of the machxo2-slave fpga > to be erased. > > Signed-off-by: Johannes Zink <j.zink@xxxxxxxxxxxxxx> > --- > .../bindings/fpga/lattice,machxo2-slave.yaml | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > > diff --git a/Documentation/devicetree/bindings/fpga/lattice,machxo2-slave.yaml b/Documentation/devicetree/bindings/fpga/lattice,machxo2-slave.yaml > index d05acd6b0fc6..78f0da8f772f 100644 > --- a/Documentation/devicetree/bindings/fpga/lattice,machxo2-slave.yaml > +++ b/Documentation/devicetree/bindings/fpga/lattice,machxo2-slave.yaml > @@ -26,6 +26,19 @@ properties: > enum: > - lattice,machxo2-slave-spi > > + lattice,erase-sram: > + type: boolean > + description: SRAM is to be erased during flash erase operation > + > + lattice,erase-feature-row: > + type: boolean > + description: Feature row is to be erased during flash erase operation > + > + lattice,erase-userflash: > + type: boolean > + description: | > + UFM (user flash memory) is to be erased during flash erase operation In which conditions should we decide to erase each area? Thanks, Yilun > + > required: > - compatible > - reg > @@ -42,5 +55,7 @@ examples: > compatible = "lattice,machxo2-slave-spi"; > spi-max-frequency = <8000000>; > reg = <0>; > + lattice,erase-sram; > + lattice,erase-feature-row; > }; > }; > -- > 2.30.2 >
