[PATCH 2/9] ARM: dts: socfpga: add Enclustra Intel AA1

[Lothar Rubusch]

On Fri, Sep 13, 2024 at 1:11 AM Marek Vasut <marex at denx.de> wrote:
>
> On 9/12/24 8:06 AM, Lothar Rubusch wrote:
> > Introduce device-tree files for Enclustra Intel AA1 SoMs and related
> > support.
> >
> > - Mercury AA1
> >
> > The setup depends on a selected boot mode. Various fragments for SD/MMC
> > and QSPI flash boot are provided.
> >
> > In combination, the following Enclustra carrier boards are supported:
> >
> > - ST1
> > - PE1
> > - PE3
> >
> > Signed-off-by: Andreas Buerkler <andreas.buerkler at enclustra.com>
> > Signed-off-by: Lothar Rubusch <l.rubusch at gmail.com>
> > ---
> >   arch/arm/dts/ME-AA1-270-2I2-D11E-NFX3.dtsi    |  14 +
> >   arch/arm/dts/ME-AA1-270-3E4-D11E-NFX3.dtsi    |  14 +
> >   arch/arm/dts/ME-AA1-480-2I3-D12E-NFX3.dtsi    |  15 +
> >   arch/arm/dts/Makefile                         |   2 +
> >   arch/arm/dts/enclustra-aa1.dts                |  32 ++
> >   .../dts/socfpga_arria10_mercury_aa1_handoff.h | 307 ++++++++++++++++++
> >   .../dts/socfpga_enclustra_mercury_aa1.dtsi    | 179 ++++++++++
> >   ...cfpga_enclustra_mercury_aa1_qspi_boot.dtsi |  18 +
> >   ...fpga_enclustra_mercury_aa1_sdmmc_boot.dtsi |  18 +
> >   .../dts/socfpga_enclustra_mercury_pe1.dtsi    |   7 +
> >   .../dts/socfpga_enclustra_mercury_pe3.dtsi    |   8 +
> >   .../dts/socfpga_enclustra_mercury_st1.dtsi    |   8 +
> Is there any chance to upstream these DTs to Linux first , and then let
> them all trickle into U-Boot through dts/upstream/ ?

This is the tricky one. In principle, as it is supposed to be build on
our side this is not the case. For the kernel, we prefer to work with
DT overlays (.dtbo) where on the u-boot side we only need some basic
functionality and not everything declared. So, currently there are
differences.

Another point here for me to understand would be the following. If I
upstream some DT files to  the kernel it might take time until they go
to anything released there. So, upstreaming u-boot would wait on that
kernel release, right? In such case, I really prefer to upstream the
DT files as is to u-boot first. Then / In parallel try  to upstream
the files to the kernel. And update the u-boot DT set to point to the
kernel DT files when they are released. Could this be an approach?

Anyway, it might be that next week, I might discuss that directly in
person to get a better idea what could be a way for me with those
u-boot files. I'm coming back to this topic then. If you find some
time, please let me know what you think about it.