Why are Device Tree Compiler source files so hard to read the way the code is broke down over lines makes it harder to read than it should be.
Is it just me?
I break down the formatting sometimes and put it all on one llne just to see the nesting. Then you can see the effects of the curly brackets.
It seems proper formatting/style of this code makes it harder to read and that seems baffling to me. Usually code formatting is to make code easier to read.
Am I broken?
Is it just me?
I break down the formatting sometimes and put it all on one llne just to see the nesting. Then you can see the effects of the curly brackets.
It seems proper formatting/style of this code makes it harder to read and that seems baffling to me. Usually code formatting is to make code easier to read.
Am I broken?
Code:
/dts-v1/;
/plugin/;
/ {
compatible = "rockchip,rk3399";
fragment@0 {
target-path = "/";
__overlay__ {
w1: onewire@0 {
compatible = "w1-gpio";
pinctrl-names = "default";
gpios = <&gpio1 1 0>;
status = "okay";
};
};
};
};
/// Header PIN 15 for One Wire on RockPro64 //////
/// dtc -I dts -O dtb rockpro64-w1-gpio.dts -o rockpro64-w1-gpio.dtbo ////