[PATCH] arm64: dts: amlogic: odroid-go-ultra: use the RK818 RTC as rtc0

[Asai, Shigeaki]

Hi Neil,

On 10/19/26, Neil Armstrong wrote:
> The vrtc was used as rtc0 because it's the defaut wakeup rtc,
> can the rk818 and rk817 wakeup the system when in system suspend ?

Thank you for the review. I did not think about wakeup, sorry. I tried
it on my board:

- s2idle: with Igor's "irqchip/meson-gpio: Allow the GPIO interrupts to
  wake the system" applied, an alarm on the RK818 RTC woke the board
  4/4, and the power key on the RK817 3/3. Without it, neither of them
  woke the board.

- deep: an alarm on the vrtc (rtc1 with this patch) woke up BL30, but
  the system did not come back to Linux, and I had to disconnect the
  battery. An alarm on the RK818 RTC and the power key did not wake it
  up at all. So deep suspend does not seem to work on this board for
  now, which looks like a separate problem.

On the other hand, the vrtc does not keep the time, and the RK817 RTC
drifts, so only the RK818 RTC gives the correct time at boot. Also,
before this patch, the vrtc was not rtc0 on my board even with the
rtc0 alias: the RK817 and RK818 RTCs registered first and took rtc0
and rtc1, and the vrtc became rtc2.

Would it be OK to keep this patch as it is? If you prefer to keep the
vrtc as rtc0 for deep suspend, I can send a v2 with rtc0 = vrtc,
rtc1 = RK818 and rtc2 = RK817 instead.

(This reply was written with the help of Claude.)

Thanks
Asai, Shigeaki