[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <14722734.oMan5NXi5u@sven-desktop>
Date: Mon, 11 Oct 2021 09:06:56 +0200
From: Sven Eckelmann <sven@...fation.org>
To: openwrt-devel@...ts.openwrt.org
Cc: Ansuel Smith <ansuelsmth@...il.com>,
Michael Walle <michael@...le.cc>,
Adrian Schmutzler <dev@...mutzler.it>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
linux-mtd@...ts.infradead.org,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
linux-kernel@...r.kernel.org
Subject: Re: nvmem: Defining cells on mtd created by mtdparts
On Sunday, 10 October 2021 14:53:13 CEST Sven Eckelmann wrote:
[...]
> Since there are most likely more devices out there which use mtdparts, I would
> guess that there might already be a strategy out there which can be used to
> define the nvmem-provider for mtdparts defined partitions. At least I saw that
> Bartosz Golaszewski added all the mtd devices automatically as nvmem provider
> in c4dfa25ab307 ("mtd: add support for reading MTD devices via the nvmem
> API"). So there might also be something for nvmem-cells to find the correct
> mtd instead of relying on the fixed-partitions registration + of_node (which
> doesn't exist because it comes from mtdparts and not devicetree).
Ansuel Smith just proposed in OpenWrt [1] a workaround. It basically adds a
minimal fixed-partitions parser to the mtd cmdlinepart parser (responsible for
the mtdparts=) that tries to find the matching (size + offset) fixed-partition
from the devicetree. The code in mtd_device_parse_register
(add_mtd_partitions -> add_mtd_device -> mtd_nvmem_add) will then
automatically take care of the rest.
Kind regards,
Sven
[1] https://github.com/openwrt/openwrt/pull/4664#issuecomment-939567963
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists