All of lore.kernel.org
 help / color / mirror / Atom feed
* PSU initialization code on zynqmp platforms
@ 2022-12-06  1:01 Graeme Smecher
  2022-12-06 10:50 ` Michal Simek
  0 siblings, 1 reply; 3+ messages in thread
From: Graeme Smecher @ 2022-12-06  1:01 UTC (permalink / raw)
  To: u-boot, michal.simek

Hi Michal,

(Well, that's embarassing. Sending again with a useful subject.)

I'm bringing up u-boot on a custom zynqmp platform. For the PSU 
initialization, I can start with the psu_init_gpl.[ch] files embedded in 
the .xsa generated by Vivado. However, these are pretty flawed [1, 2].

What is your workflow for generating and maintaining the in-tree 
psu_init_gpl files you maintain? Are these files cleaned up and 
maintained by hand?

If your workflow is functional, I will happily emulate it instead - even 
if it means straying from Vivado's configuration GUI.

best,
Graeme

1: https://lists.denx.de/pipermail/u-boot/2021-February/439394.html
2: https://support.xilinx.com/s/feed/0D52E00006kuRAMSA2

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: PSU initialization code on zynqmp platforms
  2022-12-06  1:01 PSU initialization code on zynqmp platforms Graeme Smecher
@ 2022-12-06 10:50 ` Michal Simek
  2022-12-06 17:23   ` Graeme Smecher
  0 siblings, 1 reply; 3+ messages in thread
From: Michal Simek @ 2022-12-06 10:50 UTC (permalink / raw)
  To: Graeme Smecher, u-boot

Hi,

On 12/6/22 02:01, Graeme Smecher wrote:
> Hi Michal,
> 
> (Well, that's embarassing. Sending again with a useful subject.)
> 
> I'm bringing up u-boot on a custom zynqmp platform. For the PSU initialization, 
> I can start with the psu_init_gpl.[ch] files embedded in the .xsa generated by 
> Vivado. However, these are pretty flawed [1, 2].
> 
> What is your workflow for generating and maintaining the in-tree psu_init_gpl 
> files you maintain? Are these files cleaned up and maintained by hand?
> 
> If your workflow is functional, I will happily emulate it instead - even if it 
> means straying from Vivado's configuration GUI.

I am just copy psu init files from xsa and copy it somewhere and then run
./tools/zynqmp_psu_init_minimize.sh to minimize it. And then commit and small 
manual cleanups to resolved issues reported by checkpatch.

Thanks,
Michal

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: PSU initialization code on zynqmp platforms
  2022-12-06 10:50 ` Michal Simek
@ 2022-12-06 17:23   ` Graeme Smecher
  0 siblings, 0 replies; 3+ messages in thread
From: Graeme Smecher @ 2022-12-06 17:23 UTC (permalink / raw)
  To: Michal Simek, u-boot

Hi Michal,

On 2022-12-06 02:50, Michal Simek wrote:
> Hi,
> 
> On 12/6/22 02:01, Graeme Smecher wrote:
>> Hi Michal,
>>
>> (Well, that's embarassing. Sending again with a useful subject.)
>>
>> I'm bringing up u-boot on a custom zynqmp platform. For the PSU 
>> initialization, I can start with the psu_init_gpl.[ch] files embedded 
>> in the .xsa generated by Vivado. However, these are pretty flawed [1, 2].
>>
>> What is your workflow for generating and maintaining the in-tree 
>> psu_init_gpl files you maintain? Are these files cleaned up and 
>> maintained by hand?
>>
>> If your workflow is functional, I will happily emulate it instead - 
>> even if it means straying from Vivado's configuration GUI.
> 
> I am just copy psu init files from xsa and copy it somewhere and then run
> ./tools/zynqmp_psu_init_minimize.sh to minimize it. And then commit and 
> small manual cleanups to resolved issues reported by checkpatch.

Thanks - that script is exactly what I needed to plug the gap between 
Vivado and what's in-tree.

best,
Graeme

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-12-06 17:23 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-06  1:01 PSU initialization code on zynqmp platforms Graeme Smecher
2022-12-06 10:50 ` Michal Simek
2022-12-06 17:23   ` Graeme Smecher

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.