* Andreas Kemnade <andreas@xxxxxxxxxxxx> [241108 17:41]: > They are not used, if they are just disabled, kernel does not touch > them, so if it is there, the kernel can handle > pm. At least as long as it is not under ti,sysc. > > There are probably cleaner solutions for this, but for a CC: stable I > would prefer something less invasive. For unused devices, it's best to configure things to use ti-sysc, and then set status disabled (or reserved) for the child devices only. This way the parent interconnect target module is PM runtime managed by Linux, and it's power domain gets properly idled for the unused devices too. > I can try a ti-sysc based fix in parallel. Yeah that should be trivial hopefully :) Regards, Tony
