On 18/01/2023 17:28, Jan Kiszka wrote: > From: chao zeng <chao.zeng@xxxxxxxxxxx> > > The M.2 variant comes with 2 slots, one B-keyed and another one E-keyed. > They are configured by the firmware during startup. Also the device tree > will be adjusted according to the detect or manually configured > interface mode by the firmware. The kernel only carries a single > configuration as base device tree. It has to be built with a symbols > node so that the firmware can apply overlays for the connector modes. > > Signed-off-by: chao zeng <chao.zeng@xxxxxxxxxxx> > [Jan: refactored to a single DT] > Signed-off-by: Jan Kiszka <jan.kiszka@xxxxxxxxxxx> > --- > arch/arm64/boot/dts/ti/Makefile | 3 + > .../dts/ti/k3-am6548-iot2050-advanced-m2.dts | 122 ++++++++++++++++++ > 2 files changed, 125 insertions(+) > create mode 100644 arch/arm64/boot/dts/ti/k3-am6548-iot2050-advanced-m2.dts > > diff --git a/arch/arm64/boot/dts/ti/Makefile b/arch/arm64/boot/dts/ti/Makefile > index cf7c509538a4..13e79bf7e804 100644 > --- a/arch/arm64/boot/dts/ti/Makefile > +++ b/arch/arm64/boot/dts/ti/Makefile > @@ -11,6 +11,9 @@ dtb-$(CONFIG_ARCH_K3) += k3-am6528-iot2050-basic.dtb > dtb-$(CONFIG_ARCH_K3) += k3-am6528-iot2050-basic-pg2.dtb > dtb-$(CONFIG_ARCH_K3) += k3-am6548-iot2050-advanced.dtb > dtb-$(CONFIG_ARCH_K3) += k3-am6548-iot2050-advanced-pg2.dtb > +dtb-$(CONFIG_ARCH_K3) += k3-am6548-iot2050-advanced-m2.dtb This does not look like proper order. > + > +DTC_FLAGS_k3-am6548-iot2050-advanced-m2 += -@ > Best regards, Krzysztof
