mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: mfe@pengutronix.de
Subject: [PATCH 0/5] environment: upstream-NVMEM-compliant OF binding
Date: Tue, 26 Nov 2024 16:33:07 +0100	[thread overview]
Message-ID: <20241126153312.3758355-1-a.fatoum@pengutronix.de> (raw)

While we have had our binding for a long time, it was never submitted
for upstream inclusion in the Linux DT bindings and it's unlikely to be
accepted as there are no other bindings that reference a fixed partition
in a property.

Linux has support for a u-boot,env binding, which is used by giving the
partition a compatible = "u-boot,env" property.

This series supports the same thing for barebox and allows barebox,environment
to be a subnode of a fixed-partitions node. We intentionally don't add
file-path support for now as the intention is to flesh out this binding
together with upstream.

Ahmad Fatoum (5):
  of: partition: don't parse nvmem-cells in legacy OF binding
  nvmem: probe nvmem-cells container via driver model
  environment: register barebox env OF driver regardless of /chosen
  environment: add support for a single node barebox,environment binding
  sandbox: switch to new barebox environment binding

 .../bindings/nvmem/barebox,environment.yaml   | 55 +++++++++++++
 arch/sandbox/dts/sandbox.dts                  |  8 +-
 drivers/nvmem/partition.c                     | 23 +++++-
 drivers/of/barebox.c                          | 77 +++++++++----------
 drivers/of/partition.c                        | 13 +---
 include/linux/nvmem-provider.h                |  6 --
 6 files changed, 118 insertions(+), 64 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/nvmem/barebox,environment.yaml

-- 
2.39.5




             reply	other threads:[~2024-11-26 15:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 15:33 Ahmad Fatoum [this message]
2024-11-26 15:33 ` [PATCH 1/5] of: partition: don't parse nvmem-cells in legacy " Ahmad Fatoum
2024-11-26 15:33 ` [PATCH 2/5] nvmem: probe nvmem-cells container via driver model Ahmad Fatoum
2024-11-26 15:33 ` [PATCH 3/5] environment: register barebox env OF driver regardless of /chosen Ahmad Fatoum
2024-11-26 15:33 ` [PATCH 4/5] environment: add support for a single node barebox,environment binding Ahmad Fatoum
2024-11-26 15:33 ` [PATCH 5/5] sandbox: switch to new barebox environment binding Ahmad Fatoum
2024-11-28  6:54 ` [PATCH 0/5] environment: upstream-NVMEM-compliant OF binding Sascha Hauer

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=20241126153312.3758355-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=mfe@pengutronix.de \
    /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