Skip to contentSkip to conversation

nvmem: patches (set 1) for 6.17

PATCH New [email protected] 1 participant 9 messages Jul 12, 2025

Subsystems (3)
lore
Share & tools
lore

[email protected]

author maintainer
#0 lore raw

cover nvmem: patches (set 1) for 6.17

From: Srinivas Kandagatla <[email protected]>

Here are few nvmem patches for 6.17, Could you please queue these for 6.17.

Patches include:
- adding bindings conversion to yaml for lpc1857 and vf610 providers.
- fix some typos in MODULE_AUTHOR.
- make nvmem_bus_type constant
- add bindings for A523 SID controller.
- Update fixed-layout to support optional bit position

Thanks,
Srini

Alok Tiwari (1):
nvmem: core: Fix typos in comments and MODULE_AUTHOR strings

Chen-Yu Tsai (1):
dt-bindings: nvmem: mediatek: efuse: split MT8186/MT8188 from base
version

Frank Li (2):
dt-bindings: nvmem: convert lpc1857-eeprom.txt to yaml format
dt-bindings: nvmem: convert vf610-ocotp.txt to yaml format

Greg Kroah-Hartman (1):
nvmem: make nvmem_bus_type constant

Mikhail Kalashnikov (1):
dt-bindings: nvmem: SID: Add binding for A523 SID controller

Sven Peter (2):
nvmem: apple: drop default ARCH_APPLE in Kconfig
dt-bindings: nvmem: fixed-layout: Allow optional bit positions

 .../nvmem/allwinner,sun4i-a10-sid.yaml        |  1 +
 .../bindings/nvmem/fsl,vf610-ocotp.yaml       | 47 ++++++++++++++
 .../bindings/nvmem/layouts/fixed-layout.yaml  |  2 +-
 .../bindings/nvmem/lpc1857-eeprom.txt         | 28 ---------
 .../bindings/nvmem/mediatek,efuse.yaml        | 17 +++++-
 .../bindings/nvmem/nxp,lpc1857-eeprom.yaml    | 61 +++++++++++++++++++
 .../devicetree/bindings/nvmem/vf610-ocotp.txt | 19 ------
 drivers/nvmem/Kconfig                         |  1 -
 drivers/nvmem/core.c                          | 12 ++--
 9 files changed, 131 insertions(+), 57 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/nvmem/fsl,vf610-ocotp.yaml
 delete mode 100644 Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt
 create mode 100644 Documentation/devicetree/bindings/nvmem/nxp,lpc1857-eeprom.yaml
 delete mode 100644 Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
Signature · 1 line
2.43.0
author maintainer
#1 lore raw

PATCH 1/8 nvmem: apple: drop default ARCH_APPLE in Kconfig

From: Sven Peter <[email protected]>

When the first driver for Apple Silicon was upstreamed we accidentally included default ARCH_APPLE in its Kconfig which then spread to almost every subsequent driver. As soon as ARCH_APPLE is set to y this will pull in many drivers as built-ins which is not what we want. Thus, drop default ARCH_APPLE from Kconfig.

---
 drivers/nvmem/Kconfig | 1 -
 1 file changed, 1 deletion(-)
drivers/nvmem/Kconfig +0 -1
index d370b2ad11e7..edd811444ce5 100644
@@ -31,7 +31,6 @@ source "drivers/nvmem/layouts/Kconfig"
 config NVMEM_APPLE_EFUSES
 	tristate "Apple eFuse support"
 	depends on ARCH_APPLE || COMPILE_TEST
-	default ARCH_APPLE
 	help
 	  Say y here to enable support for reading eFuses on Apple SoCs
 	  such as the M1. These are e.g. used to store factory programmed
Signature · 1 line
2.43.0
author maintainer
#2 lore raw

PATCH 2/8 dt-bindings: nvmem: fixed-layout: Allow optional bit positions

In reply to [email protected]

From: Sven Peter <[email protected]>

NVMEM nodes can optionally include the bits property to specify the bit position of the cell within a byte.
Extend patternProperties to allow adding the bit offset to the node address to be able to distinguish nodes with the same address but different bit positions, e.g.

   trim@54,4 {
        reg = <0x54 1>;
        bits = <4 2>;
    };
    trim@54,0 {
        reg = <0x54 1>;
        bits = <0 4>;
    };

Before the conversion to NVMEM layouts in commit bd912c991d2e ("dt-bindings: nvmem: layouts: add fixed-layout") this extension was originally added with commit 4b2545dd19ed ("dt-bindings: nvmem: Extend patternProperties to optionally indicate bit position") to the now deprecated layout.

---
 .../devicetree/bindings/nvmem/layouts/fixed-layout.yaml         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/devicetree/bindings/nvmem/layouts/fixed-layout.yaml +1 -1
index 9bd34bd5af30..b01567f99284 100644
@@ -27,7 +27,7 @@ properties:
     const: 1
 
 patternProperties:
-  "@[a-f0-9]+$":
+  "@[a-f0-9]+(,[0-7])?$":
     type: object
     $ref: fixed-cell.yaml
     unevaluatedProperties: false
Signature · 1 line
2.43.0
author maintainer
#3 lore raw

PATCH 3/8 nvmem: core: Fix typos in comments and MODULE_AUTHOR strings

In reply to [email protected]

From: Alok Tiwari <[email protected]>

This patch fixes minor typo issues for nvmem-core.c:
Corrects "form" to "from" in multiple function descriptions. Fixes missing closing angle brackets in MODULE_AUTHOR entries.

These changes improve readability and formatting consistency.

---
 drivers/nvmem/core.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)
drivers/nvmem/core.c +5 -5
index fd2a9698d1c9..880572ba515a 100644
@@ -1263,7 +1263,7 @@ void nvmem_device_put(struct nvmem_device *nvmem)
 EXPORT_SYMBOL_GPL(nvmem_device_put);
 
 /**
- * devm_nvmem_device_get() - Get nvmem device of device form a given id
+ * devm_nvmem_device_get() - Get nvmem device of device from a given id
  *
  * @dev: Device that requests the nvmem device.
  * @id: name id for the requested nvmem device.
@@ -1491,7 +1491,7 @@ EXPORT_SYMBOL_GPL(of_nvmem_cell_get);
 #endif
 
 /**
- * nvmem_cell_get() - Get nvmem cell of device form a given cell name
+ * nvmem_cell_get() - Get nvmem cell of device from a given cell name
  *
  * @dev: Device that requests the nvmem cell.
  * @id: nvmem cell name to get (this corresponds with the name from the
@@ -1526,7 +1526,7 @@ static void devm_nvmem_cell_release(struct device *dev, void *res)
 }
 
 /**
- * devm_nvmem_cell_get() - Get nvmem cell of device form a given id
+ * devm_nvmem_cell_get() - Get nvmem cell of device from a given id
  *
  * @dev: Device that requests the nvmem cell.
  * @id: nvmem cell name id to get.
@@ -2194,6 +2194,6 @@ static void __exit nvmem_exit(void)
 subsys_initcall(nvmem_init);
 module_exit(nvmem_exit);
 
-MODULE_AUTHOR("Srinivas Kandagatla <[email protected]");
-MODULE_AUTHOR("Maxime Ripard <[email protected]");
+MODULE_AUTHOR("Srinivas Kandagatla <[email protected]>");
+MODULE_AUTHOR("Maxime Ripard <[email protected]>");
 MODULE_DESCRIPTION("nvmem Driver Core");
Signature · 1 line
2.43.0
author maintainer
#4 lore raw

PATCH 4/8 dt-bindings: nvmem: convert lpc1857-eeprom.txt to yaml format

In reply to [email protected]

From: Frank Li <[email protected]>

Convert lpc1857-eeprom.txt to yaml format.

---
 .../bindings/nvmem/lpc1857-eeprom.txt         | 28 ---------
 .../bindings/nvmem/nxp,lpc1857-eeprom.yaml    | 61 +++++++++++++++++++
 2 files changed, 61 insertions(+), 28 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt
 create mode 100644 Documentation/devicetree/bindings/nvmem/nxp,lpc1857-eeprom.yaml
Documentation/devicetree/bindings/nvmem/lpc1857-eeprom.txt deleted +0 -28
deleted file mode 100644
index 809df68f6e14..000000000000
@@ -1,28 +0,0 @@
-* NXP LPC18xx EEPROM memory NVMEM driver
-
-Required properties:
-  - compatible: Should be "nxp,lpc1857-eeprom"
-  - reg: Must contain an entry with the physical base address and length
-    for each entry in reg-names.
-  - reg-names: Must include the following entries.
-    - reg: EEPROM registers.
-    - mem: EEPROM address space.
-  - clocks: Must contain an entry for each entry in clock-names.
-  - clock-names: Must include the following entries.
-    - eeprom: EEPROM operating clock.
-  - resets: Should contain a reference to the reset controller asserting
-    the EEPROM in reset.
-  - interrupts: Should contain EEPROM interrupt.
-
-Example:
-
-  eeprom: eeprom@4000e000 {
-    compatible = "nxp,lpc1857-eeprom";
-    reg = <0x4000e000 0x1000>,
-          <0x20040000 0x4000>;
-    reg-names = "reg", "mem";
-    clocks = <&ccu1 CLK_CPU_EEPROM>;
-    clock-names = "eeprom";
-    resets = <&rgu 27>;
-    interrupts = <4>;
-  };
Documentation/devicetree/bindings/nvmem/nxp,lpc1857-eeprom.yaml new file +61 -0

61 lines not on this page · raw message

Signature · 1 line
2.43.0
author maintainer
#5 lore raw

PATCH 5/8 nvmem: make nvmem_bus_type constant

In reply to [email protected]

From: Greg Kroah-Hartman <[email protected]>

Now that the driver core can properly handle constant struct bus_type, move the nvmem_bus_type variable to be a constant structure as well, placing it into read-only memory which can not be modified at runtime.

---
 drivers/nvmem/core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/nvmem/core.c +1 -1
index 880572ba515a..817f55f3a19e 100644
@@ -544,7 +544,7 @@ static const struct device_type nvmem_provider_type = {
 	.release	= nvmem_release,
 };
 
-static struct bus_type nvmem_bus_type = {
+static const struct bus_type nvmem_bus_type = {
 	.name		= "nvmem",
 };
 
Signature · 1 line
2.43.0
author maintainer
#6 lore raw

PATCH 6/8 dt-bindings: nvmem: SID: Add binding for A523 SID controller

In reply to [email protected]

From: Mikhail Kalashnikov <[email protected]>

The SID controller should be compatible with A64 and others SoC with 0x200 offset.

---
 .../devicetree/bindings/nvmem/allwinner,sun4i-a10-sid.yaml       | 1 +
 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/nvmem/allwinner,sun4i-a10-sid.yaml +1 -0
index 4424c3c5e75c..f67470b8a2ed 100644
@@ -27,6 +27,7 @@ properties:
           - enum:
               - allwinner,sun50i-a100-sid
               - allwinner,sun50i-h616-sid
+              - allwinner,sun55i-a523-sid
           - const: allwinner,sun50i-a64-sid
       - const: allwinner,sun50i-h5-sid
       - const: allwinner,sun50i-h6-sid
Signature · 1 line
2.43.0
author maintainer
#7 lore raw

PATCH 7/8 dt-bindings: nvmem: mediatek: efuse: split MT8186/MT8188 from base version

In reply to [email protected]

From: Chen-Yu Tsai <[email protected]>

On MT8186 and MT8188 one of the NVMEM cells contains the GPU speed bin value. In combination with the GPU OPP bindings, on these two platforms there is an implied scheme of converting the cell value to what the GPU OPP "opp-supported-hw" property matches. This does not apply to the base mediatek,efuse hardware, nor does it apply to any of the other platforms that do not have the GPU speed bin cell. The platform maintainer argues that this makes the compatibles incompatible with the base "mediatek,efuse" compatible, as shown in the link given.

Deprecate the MT8186/MT8188 + "mediatek,efuse" combination, and add new entries with MT8186 being the base model and MT8188 falling back to MT8186.

Fixes ff1df1886f43 ("dt-bindings: nvmem: mediatek: efuse: Add support for MT8188")
Cc Johnson Wang <[email protected]>
---
 .../bindings/nvmem/mediatek,efuse.yaml          | 17 +++++++++++++++--
 1 file changed, 15 insertions(+), 2 deletions(-)
Documentation/devicetree/bindings/nvmem/mediatek,efuse.yaml +15 -2
index 32b8c1eb4e80..4dc0d42df3e6 100644
@@ -24,6 +24,21 @@ properties:
 
   compatible:
     oneOf:
+      - items:
+          - const: mediatek,mt8188-efuse
+          - const: mediatek,mt8186-efuse
+      - const: mediatek,mt8186-efuse
+
+      - items:
+          - enum:
+              - mediatek,mt8186-efuse
+              - mediatek,mt8188-efuse
+          - const: mediatek,efuse
+        deprecated: true
+        description: Some compatibles also imply a decoding scheme for the
+          "gpu-speedbin" cell, and thus are not backward compatible to the
+          generic "mediatek,efuse" compatible.
+
       - items:
           - enum:
               - mediatek,mt7622-efuse
@@ -33,8 +48,6 @@ properties:
               - mediatek,mt7988-efuse
               - mediatek,mt8173-efuse
               - mediatek,mt8183-efuse
-              - mediatek,mt8186-efuse
-              - mediatek,mt8188-efuse
               - mediatek,mt8192-efuse
               - mediatek,mt8195-efuse
               - mediatek,mt8516-efuse
Signature · 1 line
2.43.0
author maintainer
#8 lore raw

PATCH 8/8 dt-bindings: nvmem: convert vf610-ocotp.txt to yaml format

In reply to [email protected]

From: Frank Li <[email protected]>

Convert vf610-ocotp.txt to yaml format.

Additional changes:
- Remove label in examples.
- Add include file in examples.
- Move reg just after compatible in examples.
- Add ref: nvmem.yaml and nvmem-deprecated-cells.yaml
- Remove #address-cells and #size-cells from required list to match existed dts file.

---
 .../bindings/nvmem/fsl,vf610-ocotp.yaml       | 47 +++++++++++++++++++
 .../devicetree/bindings/nvmem/vf610-ocotp.txt | 19 --------
 2 files changed, 47 insertions(+), 19 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/nvmem/fsl,vf610-ocotp.yaml
 delete mode 100644 Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt
Documentation/devicetree/bindings/nvmem/fsl,vf610-ocotp.yaml new file +47 -0
new file mode 100644
index 000000000000..5aef86a752a6
@@ -0,0 +1,47 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/nvmem/fsl,vf610-ocotp.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: On-Chip OTP Memory for Freescale Vybrid
+
+maintainers:
+  - Frank Li <[email protected]>
+
+allOf:
+  - $ref: nvmem.yaml#
+  - $ref: nvmem-deprecated-cells.yaml
+
+properties:
+  compatible:
+    items:
+      - enum:
+          - fsl,vf610-ocotp
+      - const: syscon
+
+  reg:
+    maxItems: 1
+
+  clocks:
+    items:
+      - description: ipg clock we associate with the OCOTP peripheral
+
+required:
+  - compatible
+  - reg
+  - clocks
+
+unevaluatedProperties: false
+
+examples:
+  - |
+    #include <dt-bindings/clock/vf610-clock.h>
+
+    ocotp@400a5000 {
+        compatible = "fsl,vf610-ocotp", "syscon";
+        reg = <0x400a5000 0xcf0>;
+        #address-cells = <1>;
+        #size-cells = <1>;
+        clocks = <&clks VF610_CLK_OCOTP>;
+    };
Documentation/devicetree/bindings/nvmem/vf610-ocotp.txt deleted +0 -19
deleted file mode 100644
index 72ba628f6d0b..000000000000
@@ -1,19 +0,0 @@
-On-Chip OTP Memory for Freescale Vybrid
-
-Required Properties:
-  compatible:
-  - "fsl,vf610-ocotp", "syscon" for VF5xx/VF6xx
-  #address-cells : Should be 1
-  #size-cells : Should be 1
-  reg : Address and length of OTP controller and fuse map registers
-  clocks : ipg clock we associate with the OCOTP peripheral
-
-Example for Vybrid VF5xx/VF6xx:
-
-	ocotp: ocotp@400a5000 {
-		compatible = "fsl,vf610-ocotp", "syscon";
-		#address-cells = <1>;
-		#size-cells = <1>;
-		reg = <0x400a5000 0xCF0>;
-		clocks = <&clks VF610_CLK_OCOTP>;
-	};
Signature · 1 line
2.43.0