Home
last modified time | relevance | path

Searched hist:"78 f6fecdd962b564bf2cc8e2636de9e7d41ade84" (Results 1 – 3 of 3) sorted by relevance

/linux/arch/arm64/boot/dts/freescale/
H A Dfsl-ls1028a-kontron-sl28-var3.dts78f6fecdd962b564bf2cc8e2636de9e7d41ade84 Wed Apr 03 10:38:12 CEST 2024 Michael Walle <mwalle@kernel.org> arm64: dts: ls1028a: sl28: split variant 3/ads2 carrier

The devicetree files can be (re-)used in u-boot now, they are imported
on a regular basis (see OF_UPSTREAM option) there. Up until now, it
didn't matter for linux and there was just a combined devicetree
"-var3-ads2" (with ads2 being the carrier board). But if the devicetree
files are now reused in u-boot, we need to have an individual "-var3"
variant, because the bootloader is just using the bare "varN" devicetree
files. Split the "var3" off of the "-var3-ads2" devicetree.

Signed-off-by: Michael Walle <mwalle@kernel.org>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
H A Dfsl-ls1028a-kontron-sl28-var3-ads2.dtsdiff 78f6fecdd962b564bf2cc8e2636de9e7d41ade84 Wed Apr 03 10:38:12 CEST 2024 Michael Walle <mwalle@kernel.org> arm64: dts: ls1028a: sl28: split variant 3/ads2 carrier

The devicetree files can be (re-)used in u-boot now, they are imported
on a regular basis (see OF_UPSTREAM option) there. Up until now, it
didn't matter for linux and there was just a combined devicetree
"-var3-ads2" (with ads2 being the carrier board). But if the devicetree
files are now reused in u-boot, we need to have an individual "-var3"
variant, because the bootloader is just using the bare "varN" devicetree
files. Split the "var3" off of the "-var3-ads2" devicetree.

Signed-off-by: Michael Walle <mwalle@kernel.org>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
H A DMakefilediff 78f6fecdd962b564bf2cc8e2636de9e7d41ade84 Wed Apr 03 10:38:12 CEST 2024 Michael Walle <mwalle@kernel.org> arm64: dts: ls1028a: sl28: split variant 3/ads2 carrier

The devicetree files can be (re-)used in u-boot now, they are imported
on a regular basis (see OF_UPSTREAM option) there. Up until now, it
didn't matter for linux and there was just a combined devicetree
"-var3-ads2" (with ads2 being the carrier board). But if the devicetree
files are now reused in u-boot, we need to have an individual "-var3"
variant, because the bootloader is just using the bare "varN" devicetree
files. Split the "var3" off of the "-var3-ads2" devicetree.

Signed-off-by: Michael Walle <mwalle@kernel.org>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>