12:34 <psi50> Hi!

12:34 <psi50> I noticed that rtc-meson-vrtc does not support set_time. I think it would be possible to make this work by implementing LEGACY_SCPI_CMD_SET_RTC and LEGACY_SCPI_CMD_GET_RTC support in arm_scpi.

12:34 <psi50> Has anybody looked into this?

12:40 <xdarklight> psi50: not sure if anyone has looked into this yet. I'd start by checking if Amlogic's SCPI firmware actually implements _{GET_SET}_RTC. my understanding is that Amlogic implemented their SCPI firmware based on a non-released SCPI specification. also not all commands are mandatory in the specification. so before working on the Linux driver side I think it's best to check the firmware side

13:23 <narmstrong> psi50: the VRTC is a pure "virtual" rtc to trigger wake up events

13:23 <narmstrong> it's has no HW RTC (HW time storage) capabilities, only wake after a certain amount of seconds

13:27 <psi50> narmstrong: So that would mean there is no work planned to make the system store the date when a warm reboot is performed? Currently "hwclock -w" returns -EINVAL.

13:27 <narmstrong> psi50: unless there's a RTC on board, no it's not supported by the SoC

13:29 <psi50> narmstrong: Okay, thank you! I was just looking at some patches from the vendor kernel which used these SET_RTC and GET_RTC commands which is why I was curious if anything is planned for this or not.

13:38 <narmstrong> psi50: perhaps vendor has a Optee TA that can store the time, but I'm not aware of that

14:43 <psi50> Just for reference, I was referring to this commit, which adds the RTC functionality: https://github.com/StreamUnlimited/linux/commit/6ed1001786e90dd46d92d0cdf83606cd8b8a6530

14:50 <narmstrong> psi50: yep, I think those SCPI commands a for newer SoCs, I mean newer than G12B/SM1

15:12 <chewitt> "This is the Amlogic virtual Real Time Clock driver, which only has alarm function." <= from Kconfig

15:13 <chewitt> the dts entries are only setting the registers for alarm/timer and the base dateTime to increment from 1/1/1970