#asahi-dev · 2024-09-13 01:40
nickchanprobably gonna add a new property to the cluster cpufreq node specifying the highest ecore pstate#asahi-dev · 2024-09-13 01:40
nickchanthis may be tricky too because this means the cpu across cluster are related_cpus but not completely related#asahi-dev · 2024-09-13 01:36
nickchanthere might be some other stuff too when I am 100% sure I will modify the cpufreq driver to account for this#asahi-dev · 2024-09-13 01:34
nickchanwhen the pcores are not at their lowest frequency, the ecores can only be at their highest frequency#asahi-dev · 2024-09-13 01:33
nickchanwhen the ecore is not at its highest frequency, the pcores can only be at their lowest frequency#asahi-dev · 2024-09-13 01:33
nickchanthis means that:#asahi-dev · 2024-09-13 01:33
nickchanbut all cores can be active at the same time#asahi-dev · 2024-09-13 01:33
nickchan- thirdly the performance controller is still like a10 where low states represent ecore and high states represent pcore#asahi-dev · 2024-09-13 01:32
nickchan- secondly the mpidr for cpu4 and cpu5 are 0x10004 and 0x10005 respectively#asahi-dev · 2024-09-13 01:32
nickchan- first the aic does not support cluster fast ipi#asahi-dev · 2024-09-13 01:32
nickchana11 acts like as if it has like 1.5 clusters in all sorts of ways#asahi-dev · 2024-09-12 14:56
nickchanthis will fix the issue https://paste.debian.net/hidden/8c917f99/#asahi-dev · 2024-09-12 14:56
nickchanjannau: your cpuidle disable on a7-a11 generates a null deref because pdev is not initialized#asahi-dev · 2024-09-12 13:38
nickchanj`ey: maybe the comments can help but that gets the frequencies from the dt#asahi-dev · 2024-09-12 13:37
j`eyhttps://github.com/AsahiLinux/linux/blob/asahi/drivers/cpufreq/apple-soc-cpufreq.c that may help?#asahi-dev · 2024-09-12 13:35
nickchanis it possible to get the cpu frequency from the hw?#asahi-dev · 2024-09-12 11:39
nickchangoing to include an expanded version of ordering explaination from jannau's series to add m2 device trees#asahi-dev · 2024-09-12 09:57
svenideally consistent overall if someone really wants to fix that :D#asahi-dev · 2024-09-12 09:57
svenconsistent within a file, so either alphabetical or by release#asahi-dev · 2024-09-12 09:35
nickchanedit: swap a7 and desktop chips above#asahi-dev · 2024-09-12 09:34
nickchanalphabetical A9 -> (desktop chips) -> A7 -> A8 -> A10 isn't very readable for the asahi-soc reviwer, I think#asahi-dev · 2024-09-12 09:33
nickchanim more inclined to have a logical order#asahi-dev · 2024-09-12 09:32
nickchanthese changes are to be merged through asahi-soc i think#asahi-dev · 2024-09-12 09:31
nickchanv2 will be this weekend#asahi-dev · 2024-09-12 09:28
nickchanI think you should make a reply on the mailing list#asahi-dev · 2024-09-12 09:28
nickchansven: Well, the thing is the existing entries are *not* consistent #asahi-dev · 2024-09-12 08:23
svenI don’t care about the order as long as it’s consistent #asahi-dev · 2024-09-12 02:25
nickchannicolas17: chassis-type is a relatively recent thing#asahi-dev · 2024-09-12 00:41
chadmed__all the documentation said that it should _not_ do this#asahi-dev · 2024-09-12 00:41
chadmed__it took until [whenever i fixed it] for anyone to realise that opp-microwatt used to just straight up be ignored by the system if it wasnt part of a "well formed" vrm node#asahi-dev · 2024-09-12 00:40
chadmed__half the upstream devicetrees dont even bother with correct/good information in the devicetree :p #asahi-dev · 2024-09-12 00:08
nicolas17nickchan: I guess the many Linux-based set-top boxes aren't bothering with correct information in the device tree? :P#asahi-dev · 2024-09-11 18:46
nickchanhttps://lore.kernel.org/asahi/a3849bc0-000a-4290-b2c3-71a50a750495@gmail.com#asahi-dev · 2024-09-11 18:46
nickchanCan we get a clarification on how Asahi-related devicetree bindings are supposed to be sorted? It seems to be a mix of alphabetical and logical (SoC type and generation) sorting right now.#asahi-dev · 2024-09-11 15:32
nickchanwell DT spec accepts github PRs so that's easy!#asahi-dev · 2024-09-11 14:28
nickchanI think for Apple TV a new chassis-type is actually needed#asahi-dev · 2024-09-11 14:11
nickchanwell, it was added to the makefile then removed by the commit to add t8011 #asahi-dev · 2024-09-11 13:59
nickchant8010-n112.dts not being in the makefile and missing an include#asahi-dev · 2024-09-11 13:58
nickchan... right stuff went wrong it really isn't possible to get things right the first type#asahi-dev · 2024-09-11 13:33
chaos_princessand also root menu, which seems like it fits, but idk if anything listens for that one#asahi-dev · 2024-09-11 13:33
chaos_princessoh, for menu i got it wrong, there is menu and context menu#asahi-dev · 2024-09-11 13:32
nickchanlike apple tv#asahi-dev · 2024-09-11 13:32
nickchanI guess I can use embedded when nothing else fits#asahi-dev · 2024-09-11 13:32
nickchanchassis-type: desktop, laptop, convertible, server, tablet, handset, watch, embedded#asahi-dev · 2024-09-11 13:31
nickchani mean homepage worked fine for the key at the bottom of the samsung galaxy a7#asahi-dev · 2024-09-11 13:30
nickchanahaha then those wouldn't fit and KEY_HOMEPAGE should be used#asahi-dev · 2024-09-11 13:30
chaos_princessthough homepage is also a bit of HID abuse, back in the day some keyboards shipped with a key that opened ie homepage, and it is that#asahi-dev · 2024-09-11 13:29
chaos_princessiirc home and menu are the literal home button on the keyboard and the contextual menu key from a normal pc keyboard respectively#asahi-dev · 2024-09-11 13:29
nickchanbut Apple TV ?#asahi-dev · 2024-09-11 13:29
nickchannow for iPhones, iPads and iPod touches it is pretty obvious