rtc modules are loaded after controller-runtime tries to use them

[nberlee]

Bug Report

When I compile the rtc-hym8562 driver as a module, it initializes too late. However, there's no issue when it's built into the kernel.

Description

This issue presents itself regardless of whether the rtc-hym8562 driver is automatically detected or manually configured to load in Talos. In this configuration, the driver initialization is delayed, leading to controller-runtime not able to use the Real-Time Clock (RTC) device. Conversely, when the rtc-hym8562 driver is directly built into the kernel, this problem does not manifest, and the RTC device is detected and initialized without any delays.

Logs

 [2023-12-15T12:27:09.499321693Z]: [talos] failure opening RTC, ignored {"component": "controller-runtime", "controller": "time.SyncController", "error": "no RTC device found"}
 [2023-12-15T12:27:16.426228693Z]: rtc-hym8563 2-0051: registered as rtc0
 [2023-12-15T12:27:16.462028693Z]: rtc-hym8563 2-0051: setting system clock to 2023-12-15T12:27:16 UTC (1702643236)

Environment

• Talos version: 1.6.0-beta.1
• Platform: arm64