From: Daniel Schultz <d.schultz@phytec.de>
To: <u-boot@lists.denx.de>, <trini@konsulko.com>, <upstream@lists.phytec.de>
Cc: <w.egorov@phytec.de>, <t.remmet@phytec.de>, <d-gole@ti.com>,
Daniel Schultz <d.schultz@phytec.de>
Subject: [PATCH v2 0/9] Generalize PHYTEC Overlay Handling
Date: Tue, 16 Jul 2024 22:11:25 -0700 [thread overview]
Message-ID: <20240717051134.1538180-1-d.schultz@phytec.de> (raw)
The overlays are specified in the bootenv.txt file that is loaded into
the environment. Then these overlays get loaded and applied via a script.
These scripts for loading and applying devicetree overlays are identical
for many phytec boards.
Create a common overlays.env that can be included.
Add support for devicetree overlays to phycore-imx8mp and include the
overlays.env for phycore-imx93.
Rename existing environment variables according to bootstd doc.
Move MMC boot logic into a common k3_mmc.env file and include the new
overlays.env file as well.
Changes v2:
* Rebased to master and resolved a conflict in
configs/phycore-imx8mp_defconfig.
Benjamin Hahn (5):
include: env: phytec: Create env file for loading and applying
overlays
phycore-imx8mp: Add overlay and bootenv.txt support
phycore_imx93: include common overlays.env
board: phytec: renaming of variables according to bootstd doc
include: env: phytec: renaming of variables according to bootstd doc
Daniel Schultz (4):
include: env: phytec: Add common mmc boot for K3 SoMs
include: env: phytec: k3_mmc: Apply overlays during boot
board: phytec: phycore_am62x: Use k3_mmc.env logic
board: phytec: phycore_am64x: Use k3_mmc.env logic
board/phytec/phycore_am62x/phycore_am62x.env | 11 +----
board/phytec/phycore_am64x/phycore_am64x.env | 12 +----
.../phytec/phycore_imx8mp/phycore_imx8mp.env | 27 ++++++++---
board/phytec/phycore_imx93/phycore_imx93.env | 45 +++++--------------
configs/phycore-imx8mp_defconfig | 4 +-
include/env/phytec/k3_mmc.env | 21 +++++++++
include/env/phytec/overlays.env | 38 ++++++++++++++++
7 files changed, 97 insertions(+), 61 deletions(-)
create mode 100644 include/env/phytec/k3_mmc.env
create mode 100644 include/env/phytec/overlays.env
--
2.25.1
next reply other threads:[~2024-07-17 5:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 5:11 Daniel Schultz [this message]
2024-07-17 5:11 ` [PATCH v2 1/9] include: env: phytec: Create env file for loading and applying overlays Daniel Schultz
2024-07-17 5:11 ` [PATCH v2 2/9] phycore-imx8mp: Add overlay and bootenv.txt support Daniel Schultz
2024-07-17 5:11 ` [PATCH v2 3/9] phycore_imx93: include common overlays.env Daniel Schultz
2024-07-17 5:11 ` [PATCH v2 4/9] board: phytec: renaming of variables according to bootstd doc Daniel Schultz
2024-07-17 5:11 ` [PATCH v2 5/9] include: env: " Daniel Schultz
2024-07-17 5:11 ` [PATCH v2 6/9] include: env: phytec: Add common mmc boot for K3 SoMs Daniel Schultz
2024-07-17 5:11 ` [PATCH v2 7/9] include: env: phytec: k3_mmc: Apply overlays during boot Daniel Schultz
2024-07-17 5:11 ` [PATCH v2 8/9] board: phytec: phycore_am62x: Use k3_mmc.env logic Daniel Schultz
2024-07-17 5:11 ` [PATCH v2 9/9] board: phytec: phycore_am64x: " Daniel Schultz
2024-07-23 21:04 ` [PATCH v2 0/9] Generalize PHYTEC Overlay Handling Tom Rini
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=20240717051134.1538180-1-d.schultz@phytec.de \
--to=d.schultz@phytec.de \
--cc=d-gole@ti.com \
--cc=t.remmet@phytec.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=upstream@lists.phytec.de \
--cc=w.egorov@phytec.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