From: Michal Simek <michal.simek@xilinx.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Tom Rini" <trini@konsulko.com>, "Simon Glass" <sjg@chromium.org>
Cc: "Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>,
"Ricardo Salveti" <ricardo@foundries.io>,
"Michal Simek" <michal.simek@xilinx.com>,
"Jorge Ramirez-Ortiz" <jorge@foundries.io>,
devicetree@vger.kernel.org, u-boot@lists.denx.de,
linux-kernel@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH] dt-bindings: nvmem: add U-Boot environment variables binding
Date: Tue, 15 Feb 2022 15:02:24 +0100 [thread overview]
Message-ID: <193f9354-5e1d-def8-c8ab-fbe88d8d9b8f@xilinx.com> (raw)
In-Reply-To: <20220215134925.32691-1-zajec5@gmail.com>
On 2/15/22 14:49, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> U-Boot uses environment variables for storing device setup data on
> flash. That data usually needs to be accessed by a bootloader, kernel
> and often user-space.
>
> This binding allows describing environment data location and its format
> clearly. In some/many cases it should be cleaner than hardcoding &
> duplicating that info in multiple places. Bootloader & kernel can share
> DTS and user-space can try reading it too or just have correct data
> exposed by a kernel.
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> .../devicetree/bindings/nvmem/u-boot,env.yaml | 58 +++++++++++++++++++
> MAINTAINERS | 5 ++
> 2 files changed, 63 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/nvmem/u-boot,env.yaml
>
> diff --git a/Documentation/devicetree/bindings/nvmem/u-boot,env.yaml b/Documentation/devicetree/bindings/nvmem/u-boot,env.yaml
> new file mode 100644
> index 000000000000..a2b3a9b88eb8
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/u-boot,env.yaml
> @@ -0,0 +1,58 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/nvmem/u-boot,env.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: U-Boot environment variables
> +
> +description: |
> + U-Boot uses environment variables to store device parameters and
> + configuration. They may be used for booting process, setup or keeping end user
> + info.
> +
> + Data is stored on flash in a U-Boot specific format (header and NUL separated
> + key-value pairs).
> +
> + This binding allows specifying data location and used format.
> +
> +maintainers:
> + - Rafał Miłecki <rafal@milecki.pl>
> +
> +allOf:
> + - $ref: nvmem.yaml#
> +
> +properties:
> + compatible:
> + oneOf:
> + - description: A standalone env data block
> + const: u-boot,env
> + - description: Two redundant blocks with active one flagged
> + const: u-boot,env-redundant-bool
> + - description: Two redundant blocks with active having higher counter
> + const: u-boot,env-redundant-count
I am not convinced that this is the best way how to do it. Because in u-boot
implementation you would have to enable MTD partitions to get there.
And the whole parsing will take a lot of time.
I think the way how I think this can be handled is.
# I don't think that discussion with Simon was finished.
But for example (chosen or firmware node)
chosen {
u-boot {
u-boot,env = <&qspi &part0>;
u-boot,env-redundant = <&qspi &part1>;
#or
u-boot,env = <&qspi 0 40000>;
u-boot,env-redundant = <&qspi 40000 40000>;
#or
u-boot,env = <&mmc 0 0 10000>; #device/start/size - raw mode
u-boot,env = <&mmc 0 1>; # device/partition - as file to FS
#etc.
};
};
&qspi {
flash {
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
part0: partition@0 {
label = "u-boot-env";
reg = <0x0 0x40000>;
};
part1: partition@40000 {
label = "u-boot-env-redundant";
reg = <0x40000 0x10000>;
};
};
};
Thanks,
Michal
next prev parent reply other threads:[~2022-02-15 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 13:49 Rafał Miłecki
2022-02-15 14:02 ` Michal Simek [this message]
2022-02-15 14:57 ` Sean Anderson
2022-02-15 15:02 ` Michal Simek
2022-02-16 12:59 ` Rafał Miłecki
2022-02-16 14:28 ` Michal Simek
2022-02-16 12:54 ` Rafał Miłecki
2022-02-16 14:24 ` Michal Simek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=193f9354-5e1d-def8-c8ab-fbe88d8d9b8f@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=jorge@foundries.io \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=ricardo@foundries.io \
--cc=robh+dt@kernel.org \
--cc=sjg@chromium.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=zajec5@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®