On Thu, May 07, 2026 at 05:24:36PM +0200, Loic Poulain wrote: > Add support for an nvmem-layout subnode under an eMMC hardware > partition. This allows the partition to be exposed as an NVMEM > provider and its internal layout to be described. For example, > an eMMC boot partition can be used to store device-specific > information such as a WiFi MAC address. > > Signed-off-by: Loic Poulain <[email protected]> > --- > .../devicetree/bindings/mmc/mmc-card.yaml | 24 > ++++++++++++++++++++++ > 1 file changed, 24 insertions(+) > > diff --git a/Documentation/devicetree/bindings/mmc/mmc-card.yaml > b/Documentation/devicetree/bindings/mmc/mmc-card.yaml > index > a61d6c96df759102f9c1fbfd548b026a77921cae..b21426a49cf1d9aae5b4e8e447b5be11b08c96bf > 100644 > --- a/Documentation/devicetree/bindings/mmc/mmc-card.yaml > +++ b/Documentation/devicetree/bindings/mmc/mmc-card.yaml > @@ -40,6 +40,9 @@ patternProperties: > contains: > const: fixed-partitions > > + nvmem-layout: > + $ref: /schemas/nvmem/layouts/nvmem-layout.yaml > + > required: > - compatible > - reg > @@ -86,6 +89,27 @@ examples: > read-only; > }; > }; > + > + partitions-boot2 {
Shouldn't this have a 'fixed-partitions' compatible? I'm not sure if it's an oversight in the schema that 'compatible' is not required here. It would be odd that compatible is optional, but if it is present, it must contain 'fixed-partitions' compatible. A follow-up to fix that would be great. Reviewed-by: Rob Herring (Arm) <[email protected]> Rob
