Changes in Kconfig

5f158112 - nvmem: layouts: add U-Boot env layout

Mon, 02 Sep 2024 14:29:47 +0000

nvmem: layouts: add U-Boot env layoutU-Boot environment variables are stored in a specific format. Actualdata can be placed in various storage sources (MTD, UBI volume, EEPROM,NVRAM, etc.).Move all generic (NVMEM device independent) code from NVMEM devicedriver to an NVMEM layout driver. Then add a simple NVMEM layout code ontop of it.This allows using NVMEM layout for parsing U-Boot env data stored in anykind of NVMEM device.The old NVMEM glue driver stays in place for handling bindings in theMTD context. To avoid code duplication it uses exported layout parsingfunction. Please note that handling MTD & NVMEM layout bindings may berefactored in the future.Signed-off-by: Rafał Miłecki Reviewed-by: Miquel Raynal Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20240902142952.71639-5-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/layouts/Kconfig

fc29fd82 - nvmem: core: Rework layouts to become regular devices

Fri, 15 Dec 2023 11:15:32 +0000

nvmem: core: Rework layouts to become regular devicesCurrent layout support was initially written without modules support inmind. When the requirement for module support rose, the existing basewas improved to adopt modularization support, but kind of a design flawwas introduced. With the existing implementation, when a storage deviceregisters into NVMEM, the core tries to hook a layout (if any) andpopulates its cells immediately. This means, if the hardware descriptionexpects a layout to be hooked up, but no driver was provided for that,the storage medium will fail to probe and try later fromscratch. Even if we consider that the hardware description shall becorrect, we could still probe the storage device (especially if itcontains the rootfs).One way to overcome this situation is to consider the layouts asdevices, and leverage the native notifier mechanism. When a new NVMEMdevice is registered, we can populate its nvmem-layout child, if any,and wait for the matching to be done in order to get the cells (thewaiting can be easily done with the NVMEM notifiers). If the layoutdriver is compiled as a module, it should automatically be loaded. Thisway, there is no strong order to enforce, any NVMEM device creationor NVMEM layout driver insertion will be observed as a new event whichmay lead to the creation of additional cells, without disturbing theprobes with costly (and sometimes endless) deferrals.In order to achieve that goal we create a new bus for the nvmem-layoutswith minimal logic to match nvmem-layout devices with nvmem-layoutdrivers. All this infrastructure code is created in the layouts.c file.Signed-off-by: Miquel Raynal Tested-by: Rafał Miłecki Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20231215111536.316972-7-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/layouts/Kconfig

d3c0d12f - nvmem: layouts: onie-tlv: Add new layout driver

Tue, 04 Apr 2023 17:21:31 +0000

nvmem: layouts: onie-tlv: Add new layout driverThis layout applies on top of any non volatile storage device containingan ONIE table factory flashed. This table follows the tlv(type-length-value) organization described in the link below. We cannotafford using regular parsers because the content of these tables ismanufacturer specific and must be dynamically discovered.Link: https://opencomputeproject.github.io/onie/design-spec/hw_requirements.htmlSigned-off-by: Miquel Raynal Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20230404172148.82422-24-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/layouts/Kconfig

d9fae023 - nvmem: layouts: sl28vpd: Add new layout driver

Tue, 04 Apr 2023 17:21:29 +0000

nvmem: layouts: sl28vpd: Add new layout driverThis layout applies to the VPD of the Kontron sl28 boards. The VPD onlycontains a base MAC address. Therefore, we have to add an individualoffset to it. This is done by taking the second argument of the nvmemphandle into account. Also this let us checking the VPD version and thechecksum.Signed-off-by: Michael Walle Signed-off-by: Miquel Raynal Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20230404172148.82422-22-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/layouts/Kconfig

266570f4 - nvmem: core: introduce NVMEM layouts

Tue, 04 Apr 2023 17:21:21 +0000

nvmem: core: introduce NVMEM layoutsNVMEM layouts are used to generate NVMEM cells during runtime. Think ofan EEPROM with a well-defined conent. For now, the content can bedescribed by a device tree or a board file. But this only works if theoffsets and lengths are static and don't change. One could also arguethat putting the layout of the EEPROM in the device tree is the wrongplace. Instead, the device tree should just have a specific compatiblestring.Right now there are two use cases: (1) The NVMEM cell needs special processing. E.g. if it only specifies a base MAC address offset and you need to add an offset, or it needs to parse a MAC from ASCII format or some proprietary format. (Post processing of cells is added in a later commit). (2) u-boot environment parsing. The cells don't have a particular offset but it needs parsing the content to determine the offsets and length.Co-developed-by: Miquel Raynal Signed-off-by: Miquel Raynal Signed-off-by: Michael Walle Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20230404172148.82422-14-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/layouts/Kconfig