Rafał Miłecki 5f15811286 nvmem: layouts: add U-Boot env layout ... U-Boot environment variables are stored in a specific format. Actual data can be placed in various storage sources (MTD, UBI volume, EEPROM, NVRAM, etc.). Move all generic (NVMEM device independent) code from NVMEM device driver to an NVMEM layout driver. Then add a simple NVMEM layout code on top of it. This allows using NVMEM layout for parsing U-Boot env data stored in any kind of NVMEM device. The old NVMEM glue driver stays in place for handling bindings in the MTD context. To avoid code duplication it uses exported layout parsing function. Please note that handling MTD & NVMEM layout bindings may be refactored in the future. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org> Link: https://lore.kernel.org/r/20240902142952.71639-5-srinivas.kandagatla@linaro.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2024-09-11 16:05:15 +02:00
..
Kconfig	nvmem: layouts: add U-Boot env layout	2024-09-11 16:05:15 +02:00
Makefile	nvmem: layouts: add U-Boot env layout	2024-09-11 16:05:15 +02:00
onie-tlv.c	nvmem: layouts: onie-tlv: drop driver owner initialization	2024-05-03 07:26:38 +02:00
sl28vpd.c	nvmem: layouts: sl28vpd: drop driver owner initialization	2024-05-03 07:26:38 +02:00
u-boot-env.c	nvmem: layouts: add U-Boot env layout	2024-09-11 16:05:15 +02:00
u-boot-env.h	nvmem: layouts: add U-Boot env layout	2024-09-11 16:05:15 +02:00