[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e62a50dfd968168015dd3e4fab896056@walle.cc>
Date: Sun, 28 Aug 2022 16:33:03 +0200
From: Michael Walle <michael@...le.cc>
To: Rafał Miłecki <rafal@...ecki.pl>
Cc: Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Shawn Guo <shawnguo@...nel.org>, Li Yang <leoyang.li@....com>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Frank Rowand <frowand.list@...il.com>,
linux-mtd@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
netdev@...r.kernel.org, Ahmad Fatoum <a.fatoum@...gutronix.de>
Subject: Re: [PATCH v1 06/14] nvmem: core: introduce NVMEM layouts
Am 2022-08-28 16:06, schrieb Rafał Miłecki:
> On 25.08.2022 23:44, Michael Walle wrote:
>> For now, the content can be
>> described by a device tree or a board file. But this only works if the
>> offsets and lengths are static and don't change.
>
> Not really true (see Broadcom's NVRAM and U-Boot's env data).
All except those two drivers don't add cells on their own. And for
these it is not possible to add non static cells, except in board
code maybe. This series make it possible to add this runtime parsing
to any NVMEM device.
-michael
Powered by blists - more mailing lists