On Wed, Feb 12, 2020 at 11:01:50AM +0100, Benedikt Spranger wrote: > On Mon, 10 Feb 2020 08:45:25 +0100 > Maxime Ripard <maxime@xxxxxxxxxx> wrote: > > > Looking at the board, it looks like it's just a daughter board to the > > lamobo-r1? > It is a daughter board. > > > If so, you can just include its DTS directly, there's no need to > > create a DTSI (an overlay is an option as well). > > Weighing up to include a DTS and overriding nodes versus splitting > out the commons into a DTSI let to the latter: > > Overriding DTB nodes is a mess since it makes it unnessesarily complex > to understand what happens and is hard to debug. I spend quite some > time of my life to get a clou, why a DTB of a board is messed up and > why changes got lost. Including DTS files is a matter of taste and none > of my flavors. I don't get it. If it's a daughter board, there's nothing to override, right? > Overlay would be an option, if there is a way to load the overlay > without touching the bootloader or during kexec. I mean, an overlay is strictly equivalent to including the DTS, so why are you ok with an overlay and not including it directly? Aside, U-Boot is able to apply overlays to the device tree before booting the kernel, you just have to change the boot command a bit. Maxime
Attachment:
signature.asc
Description: PGP signature
