On Thu, Aug 29, 2024 at 11:10:41AM +0200, Geert Uytterhoeven wrote: > Hi Krzysztof, > > On Thu, Aug 29, 2024 at 10:55 AM Krzysztof Kozlowski <krzk@xxxxxxxxxx> wrote: > > On 28/08/2024 22:10, Geert Uytterhoeven wrote: > > > On Mon, Aug 19, 2024 at 1:11 PM Krzysztof Kozlowski <krzk@xxxxxxxxxx> wrote: > > >> On Wed, Jul 31, 2024 at 09:37:36AM +0200, Geert Uytterhoeven wrote: > > >>> On Tue, Jul 30, 2024 at 6:24 PM Rob Herring <robh@xxxxxxxxxx> wrote: > > >>>> On Fri, Jul 26, 2024 at 03:38:06PM +0200, Geert Uytterhoeven wrote: > > >>>>> The R-Car E-FUSE blocks can be modelled better using the nvmem > > >>>>> framework. > > >>>>> > > >>>>> Replace the R-Car V3U example by an R-Car S4-8 ES1.2 example, to show > > >>>>> the definition of nvmem cells. While at it, drop unneeded labels from > > >>>>> the examples, and fix indentation. > > >>>>> > > >>>>> Add an entry to the MAINTAINERS file. > > >>>>> > > >>>>> Reported-by: Arnd Bergmann <arnd@xxxxxxxx> > > >>>>> Signed-off-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> > > >>>>> --- > > >>>>> v3: > > >>>>> - New. > > >>>>> > > >>>>> I would expect that the calib@144 node needs: > > >>>>> > > >>>>> #nvmem-cell-cells = <0>; > > > > So this is for mac-base... > > No, mac-base is not involved. It is because that's the only case that allows #nvmem-cell-cells in fixed-cell.yaml. While fixed-cell.yaml allows additional properties, where it is referenced in fixed-layout.yaml does not. Rob
