From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [PATCH] arm64: zynqmp: Support converting pm_cfg_obj.c
Date: Tue, 23 Jun 2020 18:08:55 +0200 [thread overview]
Message-ID: <94593a88-5cd5-059f-7749-f3f9ae99728e@xilinx.com> (raw)
In-Reply-To: <20200622204531.11301-1-brandon.maier@rockwellcollins.com>
On 22. 06. 20 22:45, Brandon Maier wrote:
> To use CONFIG_ZYNQMP_SPL_PM_CFG_OBJ_FILE, a developer must pull down the
> U-Boot source and run ./tools/zynqmp_pm_cfg_obj_convert.py to convert
> their pm_cfg_obj.c into U-Boot's PMU loader format, then feed that file
> back to U-Boot during build.
>
> Instead, by doing the conversion in U-Boot during the build, we can
> simplify the developer's build system. And it ensures that if
> zynqmp_pm_cfg_obj_convert.py is updated, the pm_cfg_obj will stay in
> sync with U-Boot.
>
> Add a config to set the file format, but leave the default as binary
> type for backwards compatibility.
Based on description I can't see the reason for it.
pmu config object should be aligned with pmu not with u-boot itself.
Also using this script is just one way how to get pmufw config object.
I personally don't use it but I can't see any issue to be in u-boot
project if others want to use it.
Thanks,
Michal
next prev parent reply other threads:[~2020-06-23 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 20:45 [PATCH] arm64: zynqmp: Support converting pm_cfg_obj.c Brandon Maier
2020-06-23 15:17 ` Luca Ceresoli
[not found] ` <CA+fik50_-6oRQTY0MdXacg=LHoKtjkBTQ+MYgK4VptDy5Njygg@mail.gmail.com>
2020-06-23 21:22 ` Fwd: " Brandon Maier
2020-06-23 21:23 ` Luca Ceresoli
2020-06-23 21:31 ` Luca Ceresoli
2020-06-23 21:46 ` [External] " Brandon Maier
2020-06-24 6:49 ` Michal Simek
2020-06-23 16:08 ` Michal Simek [this message]
[not found] ` <CA+fik51z3vVQDs23Yu7i164vzCQfJz_4jOa_k4nsY58edDHYYw@mail.gmail.com>
2020-06-23 21:23 ` Fwd: " Brandon Maier
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=94593a88-5cd5-059f-7749-f3f9ae99728e@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=u-boot@lists.denx.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