#
✕ nick:yuka
#asahi-dev · 2026-08-16 09:14
yukastride of 0x200000 would make more sense, since all of 0x200000, 0x400000, 0x600000, 0x800000 are readable
#asahi-dev · 2026-08-16 09:09
yukano, nevermind, question still stands
#asahi-dev · 2026-08-16 09:09
yukaOh
#asahi-dev · 2026-08-16 09:08
yukabut 0x300000 gives me an SError
#asahi-dev · 2026-08-16 09:08
yukaAs I read this, the 4 DCS instances on T6000 should be at 0x200000, 0x300000, 0x400000, 0x500000
#asahi-dev · 2026-08-16 09:06
yukahttps://github.com/AsahiLinux/m1n1/blob/main/src/mcc.c#L22
#asahi-dev · 2026-08-16 09:05
yukatrying to understand the T6000_DCS_OFFSET and T6000_DCS_STRIDE
#asahi-dev · 2026-08-16 08:44
yukaand then it gives the following entries: [(0x101e6e30-0x101e8ec7, enabled), (0x10000000-0x10000000, disabled), (0x101f1a5c-0x101ffc5b, enabled), (0x10000000-0x10000000, disabled)]
#asahi-dev · 2026-08-16 08:42
yukafrom top to bottom: start, end, unused/unk, enable
#asahi-dev · 2026-08-16 08:42
yukaand this makes sense if the stride is 4, then you read it as columns
#asahi-dev · 2026-08-16 08:42
yukaI noticed on t6031, the slot between 2 and 4 has range 0x10000000-0x10000000 and is _disabled_
#asahi-dev · 2026-08-16 08:41
yukathis was my previous attempt of staring at it: https://termbin.com/eiitlb
#asahi-dev · 2026-08-16 08:37
yukayay, I found a tz_regs mapping for t8140/t6040 which makes sense
#asahi-dev · 2026-08-15 18:49
yukabut I can't be fully sure how this works internally
#asahi-dev · 2026-08-15 18:48
yukapmgr regs say so
#asahi-dev · 2026-08-15 18:47
yukathe cores/clusters can hardly use less energy than when they're not turned on in the first place?
#asahi-dev · 2026-08-15 18:45
yukachaos_princess: but last time I tested, even just skipping smp_start_secondaries barely resulted in any power saving
#asahi-dev · 2026-08-15 18:40
yukadoes the semi-retention wfi actually power down the core (or cluster, if done on all cores)
#asahi-dev · 2026-08-15 18:39
yukathat's confusing?
#asahi-dev · 2026-08-15 18:39
yukaAha, this corresponds to STATE_PWRDOWN
#asahi-dev · 2026-08-15 18:38
yukahttps://github.com/AsahiLinux/linux/blob/e2e1930a9595bffafad92cec2b5504525efb9cd4/drivers/cpuidle/cpuidle-apple.c#L24
#asahi-dev · 2026-08-15 18:37
yukawhatever
#asahi-dev · 2026-08-15 18:36
yukaroulette-wfi
#asahi-dev · 2026-08-15 18:35
yukabut now we use this as anchor to define proper names for it. And I think non-retention wfi should be the one which drops to RVBAR and *not* the WFI_MODE one which cpuidle-apple uses which retains pc (that should rather be "deep wfi"?)
#asahi-dev · 2026-08-15 18:33
yukaI think setting CYC_OVRD_DISABLE_WFI_RET drops you to RVBAR after the next wfi
#asahi-dev · 2026-08-15 18:32
yukaCYC_OVRD_WFI_MODE=3 give the remaining core in the cluster the ability to boost but retains pc and sp
#asahi-dev · 2026-08-15 18:29
yukaAnd there are two bits in some of the sysregs
#asahi-dev · 2026-08-15 18:29
yukanormal arm64
#asahi-dev · 2026-08-15 18:28
yukathere are at least 3 behaviors of wfi
#asahi-dev · 2026-08-15 18:28
yukano
#asahi-dev · 2026-08-15 18:25
yukaMaybe this is where I got the term from, and matched it to the 'wfi which loses state' / what the cpuidle-apple driver does because that's what is actually needed
#asahi-dev · 2026-08-15 18:23
yukaIf we can agree on more precise terms of the possible states of a core and a cluster, and write them down somewhere that would be useful for these discussions
#asahi-dev · 2026-08-15 18:23
yukaBut this makes the difference of reaching >4GHz on my machines
#asahi-dev · 2026-08-15 18:22
yukaMaybe there is an even higher one?
#asahi-dev · 2026-08-15 18:21
yuka'sleep' = deep wfi again
#asahi-dev · 2026-08-15 18:21
yukabecause that does smp_start_secondaries and then the other cores sleep while a measurement is being done on one core of the cluster
#asahi-dev · 2026-08-15 18:20
yukaIf the core needed to be powered off, then the cpu pstate experiments in m1n1 could never measure the higher frequencies
#asahi-dev · 2026-08-15 18:19
yukacorresponds to wfi losing state and also the last core which is not in 'deep wfi' can boost high
#asahi-dev · 2026-08-15 18:19
yukaThe thing we do using the 'debug' sysreg in cpuidle-apple
#asahi-dev · 2026-08-15 18:18
yukaI don't think so?
#asahi-dev · 2026-08-15 18:18
yukaSorry with deep sleep I meant the wfi mode which loses state
#asahi-dev · 2026-08-15 18:11
yukaAs in, only the first core of each cluster can boost high
#asahi-dev · 2026-08-15 18:11
yukaAlso I wonder if xnu somehow accounts for the thing where the first core of each cluster does not enter deep sleep, and thus inhibits any other core in the cluster from boosting to a higher frequency
#asahi-dev · 2026-08-15 18:09
yuka*not allowed or don't know how
#asahi-dev · 2026-08-15 18:08
yukat8140/t6040 the same
#asahi-dev · 2026-08-15 18:08
yuka... frequency so I guess that's something.
#asahi-dev · 2026-08-15 18:08
yukaMy conclusion from looking into cpufreq on t8132 is: whatever is done in cpufreq_init() does not work as-is there. The APSC_DIS and APSC_BUSY do not behave as previously and I also couldn't find any new bit like that. Regarding the other cluster features, even if we figure out what xnu does there exactly, we're not allowed to modify them on the boot cluster. But disregarding all that, simply setting the pstate works as before and does increase the...
#asahi-dev · 2026-08-15 17:05
yukano pointers, I must have looked at the wrong area last time
#asahi-dev · 2026-08-15 17:04
yuka"7f 20 03 d5 7f 20 03 d5 7f 20 03 d5 7f 20 03 d5"
#asahi-dev · 2026-08-15 17:04
yukait's empty besides this:

plus ›