Device tree overlays cleanup by ukleinek · Pull Request #2624 · analogdevicesinc/linux

ukleinek · 2024-10-19T16:10:48Z

Following up on #2617 here comes a similar cleanup of most of the remaining overlay device tree sources. It converts all overlays that don't exist in the base branch (i.e. https://github.com/raspberrypi/linux/tree/rpi-6.1.y) and that don't contain __dormant__ nodes (as these are an extension to the device tree overlay mechanics not supported by dtc).

All changes have no effect on the semantic of the corresponding compiled overlays.

This fixes: arch/arm/boot/dts/overlays/rpi-ad5677r-overlay.dts:28.14-32.6: Warning (unit_address_format): /fragment@1/__overlay__/ad5677r@0f: unit name should not have leading 0s arch/arm/boot/dts/overlays/rpi-adxl375-overlay.dts:15.16-20.6: Warning (unit_address_format): /fragment@0/__overlay__/adxl375@053: unit name should not have leading 0s Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>

…ing existing ones There is a bug in the raspberry pi's bootloader that makes applying overlays that overwrite phandles buggy. In the adau7118-simple overlay that bug doesn't trigger, but it's still prudent to just prevent adding phandles to overlays if it's already known that the base dtb has a phandle. In this case "sound_overlay" is just a new label for a node that in the line above is already known to be labeled "sound". Using "sound" instead of "sound_overlay" results in some changes in the resulting dtbo. But when applying this dtbo to a base dtb, the only change is that the new overlayed dtb has no sound_overlay symbol. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>

…sting ones There is a bug in the raspberry pi's bootloader that makes applying overlays that overwrite phandles buggy. In the adau1761 overlay that bug doesn't trigger, but it's still prudent to just prevent adding phandles to overlays if it's already known that the base dtb has a phandle. In this case "sound_overlay" is just a new label for a node that in the line above is already known to be labeled "sound". Using "sound" instead of "sound_overlay" results in some changes in the resulting dtbo. But when applying this dtbo to a base dtb, the only change is that the new overlayed dtb has no sound_overlay symbol. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>

…ting ones There is a bug in the raspberry pi's bootloader that makes applying overlays that overwrite phandles buggy. In the ad5679r overlay that bug doesn't trigger, but it's still prudent to just prevent adding phandles to overlays if it's already known that the base dtb has a phandle. In this case "frag1" is just a new label for a node that in the line above is already known to be labeled "pwm". Using "pwm" instead of "frag1" results in some changes in the resulting dtbo. But when applying this dtbo to a base dtb, the only change is that the new overlayed dtb has no frag1 symbol and a few phandle renumberings. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>

…ing ones There is a bug in the raspberry pi's bootloader that makes applying overlays that overwrite phandles buggy. In the cn0508 overlay that bug doesn't trigger, but it's still prudent to just prevent adding phandles to overlays if it's already known that the base dtb has a phandle. In this case "frag0" and "frag1" are just new labels for nodes that in the line above is already known to be labeled "spi0_cs_pins" and "spi0" respectively. Using "spi0_cs_pins" and "spi0" instead of "frag0" and "frag1" results in some changes in the resulting dtbo. But when applying this dtbo to a base dtb, the only change is that the new overlayed dtb has no frag0 and frag1 symbols and a few phandle renumberings. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>

The two labels "frag0" and "frag1" are unused. Just drop them. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>

The label "frag0" is unused. Just drop it. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>