This device tree overlay (and also various others in the tree which have been derived from it) assign the alias rtc1 to the SoC realtime clock via its device tree path - this makes Debian and the kernel do the right thing with a fully functioning rtc at /dev/rtc0. Between the 4.19.x kernel series and the 6.1.x kernel series, the path for this changed from /ocp/rtc@44e3e000 to /ocp/interconnect@44c00000/segment@200000/target-module@3e000/rtc@0.
This change breaks backward compatibility. The parent device tree path: /__symbols__/rtc points to the correct path in both kernel series, but I don't think it's possible to utilise this in a devicetree overlay.
DRAFT - RFC
This device tree overlay (and also various others in the tree which have been derived from it) assign the alias rtc1 to the SoC realtime clock via its device tree path - this makes Debian and the kernel do the right thing with a fully functioning rtc at
/dev/rtc0. Between the 4.19.x kernel series and the 6.1.x kernel series, the path for this changed from/ocp/rtc@44e3e000to/ocp/interconnect@44c00000/segment@200000/target-module@3e000/rtc@0.This change breaks backward compatibility. The parent device tree path:
/__symbols__/rtcpoints to the correct path in both kernel series, but I don't think it's possible to utilise this in a devicetree overlay.