From: Rob Herring <robh+dt@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Krzysztof Kozlowski" <krzysztof.kozlowski@canonical.com>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Tom Rini" <trini@konsulko.com>,
"Ricardo Salveti" <ricardo@foundries.io>,
"Michal Simek" <michal.simek@xilinx.com>,
"Jorge Ramirez-Ortiz" <jorge@foundries.io>,
"U-Boot Mailing List" <u-boot@lists.denx.de>,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH RFC *RFC*] dt-bindings: add U-Boot chosen for environment data phandle
Date: Thu, 17 Feb 2022 15:15:54 -0600 [thread overview]
Message-ID: <CAL_JsqJjZRJCHDUK7Pia0ontdAGgvqgfPQgpu6A+UH+qovEJOQ@mail.gmail.com> (raw)
In-Reply-To: <20220217120856.2910-1-zajec5@gmail.com>
On Thu, Feb 17, 2022 at 6:09 AM Rafał Miłecki <zajec5@gmail.com> wrote:
>
> From: Rafał Miłecki <rafal@milecki.pl>
>
> This is RFC and request for a help & discussion.
>
> While reviewing patch for U-Boot env binding it has been mentioned that:
>
> 1. /Processing/ whole DT in U-Boot may be too much work
> Handling flash devices, partitions, their formats & NVMEM may require
> too many U-Boot drivers involved.
>
> 2. It'd be nice to have env data storage devices pointed in chosen
>
> I wrote this hacky PATCH to give a rough idea how it could look like.
>
> Please review this and let me know:
> 1. If solution with chosen + phandles is acceptable
> 2. How to properly name .yaml file
> 3. Where it put it
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> .../devicetree/bindings/u-boot,chosen.yaml | 39 +++++++++++++++++++
> 1 file changed, 39 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/u-boot,chosen.yaml
>
> diff --git a/Documentation/devicetree/bindings/u-boot,chosen.yaml b/Documentation/devicetree/bindings/u-boot,chosen.yaml
> new file mode 100644
> index 000000000000..8369da91193d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/u-boot,chosen.yaml
> @@ -0,0 +1,39 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/u-boot,chosen.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: U-Boot setup
> +
> +maintainers:
> + - Rafał Miłecki <rafal@milecki.pl>
> +
> +properties:
> + u-boot,env:
> + $ref: /schemas/types.yaml#/definitions/phandle-array
> + description: |
> + A list of storage volumes containing U-Boot environment data.
> +
> + Env data can be stored on various kinds of storage devices, e.g.:
> + 1. Raw flash partition
> + 2. UBI volume
> +
> +additionalProperties: true
> +
> +examples:
> + - |
> + chosen {
> + u-boot,env = <&env>;
You should look at the u-boot config support:
https://github.com/devicetree-org/dt-schema/commit/0986f729eff0f40a66e85ab9dfb37681bf025ac4
prev parent reply other threads:[~2022-02-17 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 12:08 [PATCH RFC *RFC*] dt-bindings: add U-Boot chosen for environment data phandle Rafał Miłecki
2022-02-17 21:15 ` Rob Herring [this message]
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=CAL_JsqJjZRJCHDUK7Pia0ontdAGgvqgfPQgpu6A+UH+qovEJOQ@mail.gmail.com \
--to=robh+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jorge@foundries.io \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=rafal@milecki.pl \
--cc=ricardo@foundries.io \
--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;
as well as URLs for NNTP newsgroup(s).