On Tue, Feb 11, 2025 at 08:37:01PM +0100, Alexander Sverdlin wrote: > Hi Inochi! > > On Mon, 2025-02-10 at 21:55 +0100, Alexander Sverdlin wrote: > > > > It would probably make sense that the whole series would go into SOC tree, > > > > even though technically nothing prevents the reboot/reset driver to come > > > > in PM/reset tree. If everything would come together, `reboot` command would > > > > work out of the box. > > > > > > > > [1] https://milkv.io/docs/duo/getting-started/duo-module-01 > > > > [2] https://github.com/milkv-duo/duo-buildroot-sdk-v2/releases/ > > > > [3] https://github.com/sophgo/sophgo-doc/releases/download/sg2000-trm-v1.01/sg2000_trm_en.pdf > > > > > > > > > > This reboot implentment across the RTC and 8051 domain, which is > > > still a big problem to be upstreamed. This should be designed > > > > Now I've got it. The problem is not in the reboot procedure, but > > rather how to model this thing in the DT, because of all these > > unrelated functions brought into two HW address spaces... > > > > > carefully and needs further discussion. Adding these two syscon > > > compatiable may be not a good idea and cause some problem. I invite > > > Yixun to this talk and he may give some useful suggestions. > > > > > > At last, I prefer this goes to an separate patch series, and > > > implement with rtc device. > > Thanks for your hints! > I've completely missed the RTC driver in progress [1]. > I will provide a patch registering the reboot handler on top of the driver > as soon as it's accepted. > > [1] https://patchwork.ozlabs.org/project/rtc-linux/patch/20240428060848.706573-3-qiujingbao.dlmu@xxxxxxxxx/ > As far as I know the RTC patch is no longer maintained. Maybe you can pick it up? The patch states can be found on: https://github.com/sophgo/linux/wiki Regards, Inochi
