Advanced users • Re: Raspberry PI5: Patch series introducing PCI, RP1 drivers to u-boot

Hello all,
Thank you for your interest to my patch-series. I'm happy that my work appears useful.
Currently I have two main things which are showstoppers for my patch-series:
1) dt bindings for all devices that were added to U-Boot. Definitely they have to be upstreamed to u-boot only when final DT-bindings appear in the Linux Kernel mainline. So I was asking about the process.
2) RP1 appears to be dependent from BAR initialization sequence, which is different in U-Boot. That's why currently we can see HACK in my patch-series.

Upstream have decided that as RP1 is a PCIe device the driver should dynamically load the relevant overlay to configure all the associated configuration, rather than it being static in the base DT file. I assume u-boot will have to replicate that too, which could be entertaining.

IIRC we're already using overlays in our project with U-Boot. Couple of overlays which enable/disable some features can be found in yocto repo. So I believe this could be done. In any case - I'll be waiting for final dt-bindings and rp1 driver.

thanks for working on this. In past the upstream work was done in Linux before the stuff in U-Boot followed. The reason is that both should use the same upstream DT bindings and this review is usually done by the (Linux) devicetree folks.

Thanks. I'll follow this link. For sure - Kernel first and then U-Boot.

.... I could only patch&compile directly within your tree
so would be cool add-on if you could create a raw patch for current or upcoming u-boot version(s).

Oh many thanks for testing this out. I was planning to make a rebase when dt-bindings will be released. I think U-boot master will got little bit further by this time. So just don't want to make extra work...

WBR,
Oleksii

Statistics: Posted by zerling — Tue Feb 11, 2025 11:06 am

---