lkml.org 
[lkml]   [2023]   [Dec]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH 2/2] dt-bindings: nvmem: u-boot,env: describe "data-size" property
Date
From: Rafał Miłecki <rafal@milecki.pl>

Describe what "data-size" means in U-Boot env context and why it may be
needed. It's a generic property but giving it some extra meaning in
U-Boot context may be helpful.

Cc: Christian Marangi <ansuelsmth@gmail.com>
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
---
.../devicetree/bindings/nvmem/u-boot,env.yaml | 10 ++++++++++
1 file changed, 10 insertions(+)

diff --git a/Documentation/devicetree/bindings/nvmem/u-boot,env.yaml b/Documentation/devicetree/bindings/nvmem/u-boot,env.yaml
index 9c36afc7084b..0006f022d0af 100644
--- a/Documentation/devicetree/bindings/nvmem/u-boot,env.yaml
+++ b/Documentation/devicetree/bindings/nvmem/u-boot,env.yaml
@@ -44,6 +44,15 @@ properties:
reg:
maxItems: 1

+ data-size:
+ description:
+ U-Boot environment data size is set and hardcoded during compilation using
+ CONFIG_ENV_SIZE. Knowing it is critical for CRC32 checksum calculation.
+
+ This property allows specifying it in case it differs from NVMEM device
+ size. It may happen if device partitioning was designed with different
+ concepts in mind (like block alignment or future-proof size).
+
bootcmd:
type: object
description: Command to use for automatic booting
@@ -76,6 +85,7 @@ examples:
env: partition@40000 {
compatible = "u-boot,env";
reg = <0x40000 0x10000>;
+ data-size = <0x4000>;

mac: ethaddr {
#nvmem-cell-cells = <1>;
--
2.35.3
\
 
 \ /
  Last update: 2023-12-13 16:47    [W:0.044 / U:0.100 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site