Changes in Makefile

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/Makefile

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/Makefile

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/Makefile

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/Makefile