#asahi-dev · 2024-09-16 13:11
nickchanthere is only one performance controller#asahi-dev · 2024-09-16 13:11
nickchanmaz: All CPUs switches at the same time#asahi-dev · 2024-09-16 13:09
nickchannothing seems to explode that horribly on the iPad 7 where I did get cpufreq to work, so maybe I can just taint the kernel during init and ignore it for now...#asahi-dev · 2024-09-16 13:08
nickchanmaz: Correct#asahi-dev · 2024-09-16 13:06
nickchanWhat changes is the MPIDR#asahi-dev · 2024-09-16 13:06
nickchanthere are two MIDR: one for A10/T2, another for A10X#asahi-dev · 2024-09-16 13:06
nickchanmaz: MIDR is not MPIDR#asahi-dev · 2024-09-16 13:03
nickchanbut now it looks like it maybe should end up in arch/arm64/kernel/cpu_errata.c...#asahi-dev · 2024-09-16 13:02
nickchanso far this is in arch/arm64/kernel/cpufeature.c#asahi-dev · 2024-09-16 12:59
nickchanapple_fusion_cursed_fixup()#asahi-dev · 2024-09-16 12:59
nickchanprobably should rename bad_aarch32_el0_fixup() to something more specific to a10 while doing this though#asahi-dev · 2024-09-16 12:58
nickchanthere's quite a bit of places in the kernel that uses mpidr though, id rather taint the kernel first to let people know about this cursed CPU#asahi-dev · 2024-09-16 12:57
nickchanA10 only has EL0 and EL1 so that's non issue#asahi-dev · 2024-09-16 12:52
nickchan*super sure#asahi-dev · 2024-09-16 12:52
nickchanprobably should ensure that it always enter in E-mode in the loader since the device tree is like that...#asahi-dev · 2024-09-16 12:52
nickchanthough I am not super suer if a changing MPIDR warrents a taint#asahi-dev · 2024-09-16 12:28
nickchanprobably right at where aarch32 el0 is disabled#asahi-dev · 2024-09-16 12:26
nickchanI am seriously considering to cause an immediate TAINT_CPU_OUT_OF_SPEC when I get around to the cpufreq stuff#asahi-dev · 2024-09-16 12:26
nickchanoh hell nah A10(X) MPIDR changes when with their p-state#asahi-dev · 2024-09-16 11:04
nickchanrevision == 3 would mean boot cmdline length 1024#asahi-dev · 2024-09-16 11:03
nickchanluckily for the newest increase in boot cmdline length you should be able to get around with checking the revision field of the BootArgs struct#asahi-dev · 2024-09-16 11:02
nickchanthere are some even older ones that have device tree issue that I have not gotten around to fixing yet...#asahi-dev · 2024-09-16 11:01
nickchanfor the BootArgs struct stuff because some very old firmwares like iBoot-2817 doesn't even have mem_size_actual I made some assumption and assumed the dram bottom to 0x800000000, then rounded things up to the nearest 256 MB#asahi-dev · 2024-09-14 18:00
nickchanthere is also a possibility that I am missing some code from the loader but idk.#asahi-dev · 2024-09-14 17:15
nickchanespecially without the luxury of access tracing#asahi-dev · 2024-09-14 17:15
nickchancan never know for sure if what you are doing is right when dealing with these hardware...#asahi-dev · 2024-09-14 17:14
nickchanoh no I think everything cpufreq related had to be retracted for now#asahi-dev · 2024-09-13 17:39
nickchanill call it 120-125ms max#asahi-dev · 2024-09-13 17:11
nickchanand the 16k devices that i have reseted in 80ms#asahi-dev · 2024-09-13 17:11
nickchanokay a8 is the worst it seems a8x is slightly faster#asahi-dev · 2024-09-13 17:03
nickchantakes 130-135 ms to reset#asahi-dev · 2024-09-13 17:02
nickchana8 is worse#asahi-dev · 2024-09-13 16:56
nickchanwill test newer ones too but i think the older the soc is the slower it is#asahi-dev · 2024-09-13 16:55
nickchangonna make it wait 150 ms just to be safe#asahi-dev · 2024-09-13 16:55
nickchana7 takes about 105-110 ms to actually reset#asahi-dev · 2024-09-13 16:39
nickchanand by not enough I mean the reboot failed messages shows then the system resets#asahi-dev · 2024-09-13 16:39
nickchani should do some experiments to increase the limit#asahi-dev · 2024-09-13 16:38
nickchanthe 50ms delay in the wdt driver isn't enough on some old socs i have tested#asahi-dev · 2024-09-13 13:37
nickchani will post them seperately later#asahi-dev · 2024-09-13 13:36
nickchancaches are not gonna be in tomorrow's v2 just because of a10#asahi-dev · 2024-09-13 13:19
nickchanmaybe just taking the pcore value is fine? to stay consistent with the frequency adjustments#asahi-dev · 2024-09-13 13:10
nickchandepending on the p-state#asahi-dev · 2024-09-13 13:10
nickchansince the p/e core pairs acts as logical cores that suddenly have their cache resized#asahi-dev · 2024-09-13 13:10
nickchanin the devicetree#asahi-dev · 2024-09-13 13:09
nickchani have no provision of describing the cache in a10#asahi-dev · 2024-09-13 13:09
nickchani just realized#asahi-dev · 2024-09-13 12:53
nickchangot some figures on a10 cpu voltage gonna add into the device tree for documentation purposes#asahi-dev · 2024-09-13 05:07
nickchanI guess maybe not since the pro/max chips has more than 1 p/e clusters#asahi-dev · 2024-09-13 04:56
nickchanhttps://www.kernel.org/doc/Documentation/devicetree/bindings/opp/opp.txt#asahi-dev · 2024-09-13 04:55
nickchanshouldn't the opp tables in apple soc all be marked with opp-shared;