Hi Andrea, The problem with this approach (loading an overlay from the RP1 PCIe driver), and it's one that I have raised with you offline, is that (unless anyone can prove otherwise) it becomes impossible to create a Pi 5 DTS file which makes use of the RP1's resources. How do you declare something as simple as a button wired to an RP1 GPIO, or fan connected to a PWM output? If this is the preferred route to upstream adoption, I would prefer it if rp1.dtso could be split in two - an rp1.dtsi similar to what we have downstream, and an rp1.dtso that #includes it. In this way we can keep the patching and duplication to a minimum. Thanks, Phil P.S. Apologies for the lack of context - your emails don't make it through to rpi-kernel-list, and gmail doesn't make it easy to interact with a mailing list.
