On 28/09/2024 14:47, Daniel Golle wrote: > Add the 'volume-is-critical' boolean property which marks a UBI volume > as critical for the device to boot. If set it prevents the user from > all kinds of write access to the volume as well as from renaming it or > detaching the UBI device it is located on. > > Signed-off-by: Daniel Golle <daniel@xxxxxxxxxxxxxx> > --- > .../devicetree/bindings/mtd/partitions/ubi-volume.yaml | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mtd/partitions/ubi-volume.yaml b/Documentation/devicetree/bindings/mtd/partitions/ubi-volume.yaml > index 19736b26056b..2bd751bb7f9e 100644 > --- a/Documentation/devicetree/bindings/mtd/partitions/ubi-volume.yaml > +++ b/Documentation/devicetree/bindings/mtd/partitions/ubi-volume.yaml > @@ -29,6 +29,15 @@ properties: > description: > This container may reference an NVMEM layout parser. > > + volume-is-critical: > + description: This parameter, if present, indicates that the UBI volume > + contains early-boot firmware images or data which should not be clobbered. > + If set, it prevents the user from renaming the volume, writing to it or > + making any changes affecting it, as well as detaching the UBI device it is > + located on, so direct access to the underlying MTD device is prevented as > + well. > + type: boolean UBI volumes are mapping to partitions 1-to-1, right? So rather I would propose to use partition.yaml - we already have read-only there with very similar description. Best regards, Krzysztof
