[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d2fa8acafac0d10c4340128e81e1a765@walle.cc>
Date: Thu, 05 Jan 2023 22:22:35 +0100
From: Michael Walle <michael@...le.cc>
To: Rafał Miłecki <zajec5@...il.com>
Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>,
NXP Linux Team <linux-imx@....com>,
Miquel Raynal <miquel.raynal@...tlin.com>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, u-boot@...ts.denx.de,
Rafał Miłecki
<rafal@...ecki.pl>
Subject: Re: [PATCH 2/3] nvmem: core: allow .read_post_process() callbacks to
adjust data length
Hi,
Am 2023-01-05 18:10, schrieb Rafał Miłecki:
> From: Rafał Miłecki <rafal@...ecki.pl>
>
> Sometimes reading NVMEM cell value involves some data reformatting. It
> requires passing updated size value to the caller. Support that.
Wouldn't it make more sense to convert that driver to
proper nvmem layouts, where
(1) you get that for free,
(2) support others storages than just mtd
(3) don't duplicate the mtd read code
-michael
Powered by blists - more mailing lists