Changes in Kconfig

1530b923 - nvmem: Add R-Car E-FUSE driver

Wed, 30 Oct 2024 14:03:10 +0000

nvmem: Add R-Car E-FUSE driverR-Car Gen4 SoCs contain fuses indicating hardware support or hardware(e.g. tuning) parameters. Add a driver to access the state of thefuses. This supports two types of hardware fuse providers: 1. E-FUSE non-volatile memory accessible through the Pin Function Controller on R-Car V3U and S4-8, 2. E-FUSE non-volatile memory accessible through OTP_MEM on R-Car V4H and V4M.The state of the cells can be read using the NVMEM framework, eitherfrom kernel space (e.g. by the Renesas UFSHCD driver), or fromuserspace.Signed-off-by: Geert Uytterhoeven Reviewed-by: Yoshihiro Shimoda Acked-by: Arnd Bergmann Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20241030140315.40562-3-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/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/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/Kconfig

c471245b - nvmem: sec-qfprom: Add Qualcomm secure QFPROM support

Wed, 23 Aug 2023 13:27:39 +0000

nvmem: sec-qfprom: Add Qualcomm secure QFPROM supportFor some of the Qualcomm SoC's, it is possible thatsome of the fuse regions or entire qfprom region isprotected from non-secure access. In such situations,the OS will have to use secure calls to read the region.With that motivation, add secure qfprom driver.Signed-off-by: Komal Bajaj Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20230823132744.350618-18-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig

23b7b491 - nvmem: Kconfig: Fix typo "drive" -> "driver"

Wed, 23 Aug 2023 13:27:36 +0000

nvmem: Kconfig: Fix typo "drive" -> "driver"Fix typo where "driver" was meant instead of "drive".While at it, also capitalize "OTP".Signed-off-by: Diederik de Haas Reviewed-by: Heiko Stuebner Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20230823132744.350618-15-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig

0861110b - nvmem: add new NXP QorIQ eFuse driver

Wed, 23 Aug 2023 13:27:34 +0000

nvmem: add new NXP QorIQ eFuse driverAdd SFP (Security Fuse Processor) read support for NXP (Freescale)QorIQ series SOC's.This patch adds support for the T1023 SOC using the SFP offset fromthe existing T1023 device tree. In theory this should also work forT1024, T1014 and T1013 which uses the same SFP base offset.Signed-off-by: Richard Alpe Reviewed-by: Niklas Söderlund Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20230823132744.350618-13-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig

22e9e6fc - nvmem: imx: support i.MX93 OCOTP

Sun, 11 Jun 2023 14:03:25 +0000

nvmem: imx: support i.MX93 OCOTPAdd i.MX93 OCOTP support. i.MX93 OCOTP has two parts: Fuse shadowblock(fsb) and fuse managed by ELE. The FSB part could be directlyaccessed with MMIO, the ELE could only be accessed with ELE API.Currently the ELE API is not ready, so NULL function callback is used,but it was tested with downstream ELE API.Signed-off-by: Peng Fan Signed-off-by: Srinivas Kandagatla Message-ID: <20230611140330.154222-22-srinivas.kandagatla@linaro.org>Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig

73bcd133 - nvmem: brcm_nvram: add .read_post_process() for MACs

Sun, 11 Jun 2023 14:03:08 +0000

nvmem: brcm_nvram: add .read_post_process() for MACs1. Parse ASCII MAC format into byte based2. Calculate relative addresses based on index argumentSigned-off-by: Rafał Miłecki Signed-off-by: Srinivas Kandagatla Message-ID: <20230611140330.154222-5-srinivas.kandagatla@linaro.org>Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig

c49f1a8a - nvmem: u-boot-env: post-process "ethaddr" env variable

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

nvmem: u-boot-env: post-process "ethaddr" env variableU-Boot environment variables are stored in ASCII format so "ethaddr"requires parsing into binary to make it work with Ethernet interfaces.This includes support for indexes to support #nvmem-cell-cells = <1>.Signed-off-by: Rafał Miłecki Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20230404172148.82422-36-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/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/Kconfig

bcd1fe07 - nvmem: xilinx: zynqmp: make modular

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

nvmem: xilinx: zynqmp: make modularThis driver has a MODULE_LICENSE but is not tristate so cannot bebuilt as a module, unlike all its peers: make it modular to match.Signed-off-by: Nick Alcock Suggested-by: Michal Simek Cc: Luis Chamberlain Cc: linux-modules@vger.kernel.orgCc: linux-kernel@vger.kernel.orgCc: Hitomi Hasegawa Cc: Srinivas Kandagatla Cc: Michal Simek Cc: linux-arm-kernel@lists.infradead.orgSigned-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20230404172148.82422-4-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig

1dc7e37b - nvmem: stm32: fix OPTEE dependency

Mon, 06 Feb 2023 13:43:56 +0000

nvmem: stm32: fix OPTEE dependencyThe stm32 nvmem driver fails to link as built-in when OPTEEis a loadable module:aarch64-linux-ld: drivers/nvmem/stm32-bsec-optee-ta.o: in function `stm32_bsec:stm32-bsec-optee-ta.c:(.text+0xc8): undefined reference to `tee_client_open_session'aarch64-linux-ld: drivers/nvmem/stm32-bsec-optee-ta.o: in function `stm32_bsec:stm32-bsec-optee-ta.c:(.text+0x1fc): undefined reference to `tee_client_open_context'Change the CONFIG_NVMEM_STM32_ROMEM definition so it can onlybe built-in if OPTEE is either built-in or disabled, andmake NVMEM_STM32_BSEC_OPTEE_TA a hidden symbol instead.Signed-off-by: Arnd Bergmann Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20230206134356.839737-23-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig

6a0bc352 - nvmem: stm32: add OP-TEE support for STM32MP13x

Mon, 06 Feb 2023 13:43:51 +0000

nvmem: stm32: add OP-TEE support for STM32MP13xFor boot with OP-TEE on STM32MP13, the communication with the secureworld no more use STMicroelectronics SMC but communication with theSTM32MP BSEC TA, for data access (read/write) or lock operation:- all the request are sent to OP-TEE trusted application,- for upper OTP with ECC protection and with word programming only each OTP are permanently locked when programmed to avoid ECC error on the second write operationSigned-off-by: Patrick Delaunay Reviewed-by: Etienne Carriere Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20230206134356.839737-18-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig

fb817c4e - nvmem: Kconfig: Fix spelling mistake "controlls" -> "controls"

Fri, 18 Nov 2022 06:39:26 +0000

nvmem: Kconfig: Fix spelling mistake "controlls" -> "controls"There is a spelling mistake in a Kconfig description. Fix it.Signed-off-by: Colin Ian King Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20221118063932.6418-8-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig

9e8f208a - nvmem: lan9662-otp: add support

Fri, 16 Sep 2022 12:20:59 +0000

nvmem: lan9662-otp: add supportAdd support for OTP controller available on LAN9662. The OTPC controlsthe access to a non-volatile memory. The size of the memory is 8KB.The OTPC can access the memory based on an offset.Implement both the read and the write functionality.Signed-off-by: Horatiu Vultur Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20220916122100.170016-13-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig

a06d9e5a - nvmem: sort config symbols alphabetically

Fri, 16 Sep 2022 12:20:55 +0000

nvmem: sort config symbols alphabetically1. Match what most subsystems do2. Simplify maintenance a bit3. Reduce amount of conflicts for new drivers patchesWhile at it unify indent level in Makefile.Signed-off-by: Rafał Miłecki Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20220916122100.170016-9-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig

28fc7c98 - nvmem: prefix all symbols with NVMEM_

Fri, 16 Sep 2022 12:20:54 +0000

nvmem: prefix all symbols with NVMEM_This unifies all NVMEM symbols. They follow one style now.Reviewed-by: Matthias Brugger Acked-by: Arnd Bergmann Signed-off-by: Rafał Miłecki Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20220916122100.170016-8-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig

d5542923 - nvmem: add driver handling U-Boot environment variables

Fri, 16 Sep 2022 12:20:48 +0000

nvmem: add driver handling U-Boot environment variablesU-Boot stores its setup as environment variables. It's a list ofkey-value pairs stored on flash device with a custom header.This commit adds an NVMEM driver that:1. Provides NVMEM access to environment vars binary data2. Extracts variables as NVMEM cellsCurrent Linux's NVMEM sysfs API allows reading whole NVMEM data block.It can be used by user-space tools for reading U-Boot env vars blockwithout the hassle of finding its location. Parsing will still need tobe re-done there.Kernel-parsed NVMEM cells can be read however by Linux drivers. This maybe useful for Ethernet drivers for reading device MAC address which isoften stored as U-Boot env variable.Reviewed-by: Ahmad Fatoum Signed-off-by: Rafał Miłecki Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20220916122100.170016-2-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig

98830350 - nvmem: microchip-otpc: add support

Wed, 06 Jul 2022 10:06:22 +0000

nvmem: microchip-otpc: add supportAdd support for Microchip OTP controller available on SAMA7G5. The OTPCcontrols the access to a non-volatile memory. The memory behind OTPC isorganized into packets, packets are composed by a fixed length header(4 bytes long) and a variable length payload (payload length is availablein the header). When software request the data at an offset in memorythe OTPC will return (via header + data registers) the whole packet thathas a word at that offset. For the OTP memory layout like below:offset OTP Memory layout . . . ... . . .0x0E +-----------+ <--- packet X | header X |0x12 +-----------+ | payload X |0x16 | | | |0x1A | | +-----------+ . . . ... . . .if user requests data at address 0x16 the data started at 0x0E will bereturned by controller. User will be able to fetch the whole packetstarting at 0x0E (or parts of the packet) via proper registers. The samepacket will be returned if software request the data at offset 0x0E or0x12 or 0x1A.The OTP will be populated by Microchip with at least 2 packets first onebeing boot configuration packet and the 2nd one being temperaturecalibration packet. The packet order will be preserved b/w different chiprevisions but the packet sizes may change.For the above reasons and to keep the same software able to work on allchip variants the read function of the driver is working with a packetid instead of an offset in OTP memory.Signed-off-by: Claudiu Beznea Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20220706100627.6534-3-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig

943eadbd - nvmem: sfp: Use regmap

Fri, 29 Apr 2022 16:27:00 +0000

nvmem: sfp: Use regmapThis converts the SFP driver to use regmap. This will allow easilysupporting devices with different endians. We disallow byte-levelaccess, as regmap_bulk_read doesn't support it (and it's unclear whatthe correct result would be when we have an endianness difference).Signed-off-by: Sean Anderson Signed-off-by: Srinivas Kandagatla Link: https://lore.kernel.org/r/20220429162701.2222-16-srinivas.kandagatla@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/nvmem/Kconfig