On Thu, Mar 21, 2024 at 07:31:48PM +0000, Daniel Golle wrote: > On embedded devices using an eMMC it is common that one or more (hw/sw) > partitions on the eMMC are used to store MAC addresses and Wi-Fi > calibration EEPROM data. > > Implement an NVMEM provider backed by a block device as typically the > NVMEM framework is used to have kernel drivers read and use binary data > from EEPROMs, efuses, flash memory (MTD), ... > > In order to be able to reference hardware partitions on an eMMC, add code > to bind each hardware partition to a specific firmware subnode. > > Overall, this enables uniform handling across practially all flash > storage types used for this purpose (MTD, UBI, and now also MMC). > > As part of this series it was necessary to define a device tree schema > for block devices and partitions on them, which (similar to how it now > works also for UBI volumes) can be matched by one or more properties. > > --- > This series has previously been submitted as RFC on July 19th 2023[1] > and most of the basic idea did not change since. Another round of RFC > was submitted on March 5th 2024[2] which has received overall positive > feedback and only minor corrections have been done since (see > changelog below). Also, please version your patches. 'RFC' is a tag, not a version. v1 was July. v2 was March 5th. This is v3. Rob
