[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a40fabd8570067426a544bf0b6ece563@walle.cc>
Date: Sun, 28 Aug 2022 16:36:57 +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: [RFC PATCH v1 13/14] nvmem: layouts: u-boot-env: add device node
Am 2022-08-28 15:55, schrieb Rafał Miłecki:
> On 25.08.2022 23:44, Michael Walle wrote:
>> Register the device node so we can actually make use of the cells from
>> within the device tree.
>>
>> This obviously only works if the environment variable name can be
>> mapped
>> to the device node, which isn't always the case. Think of "_" vs "-".
>> But for simple things like ethaddr, this will work.
>
> We probably shouldn't support undocumented syntax (bindings).
If we only support a predefined list of variables, we can make them
device tree compatible anyway. E.g. we could have a mapping
"serial-number" <-> "serial#"
-michael
> I've identical local patch that waits for
> [PATCH] dt-bindings: nvmem: u-boot,env: add basic NVMEM cells
> https://patchwork.ozlabs.org/project/devicetree-bindings/patch/20220703084843.21922-1-zajec5@gmail.com/
> to be accepted.
Powered by blists - more mailing lists