On Thu, Aug 25, 2022 at 04:13:29PM +0200, Johannes Zink wrote: > This patch introduces additional memory areas of the machxo2-slave fpga > to be erased. Why? > > 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 These seem like policy. It this something that's really static to a particular board rather than something the user would configure each time. Rob
