From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michal Simek <michal.simek@xilinx.com>
Date: Tue, 23 Jun 2020 18:08:55 +0200
Subject: [PATCH] arm64: zynqmp: Support converting pm_cfg_obj.c
In-Reply-To: <20200622204531.11301-1-brandon.maier@rockwellcollins.com>
References: <20200622204531.11301-1-brandon.maier@rockwellcollins.com>
Message-ID: <94593a88-5cd5-059f-7749-f3f9ae99728e@xilinx.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de



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