#
✕ nick:sven
#asahi-dev · 2026-08-18 14:58
svenstill hates thunderbolt
#asahi-dev · 2026-08-18 14:58
svenalso found out in the process that https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/usb/typec_tbt.h#n30 has tbt3 vs. tbt2/legacy swapped
#asahi-dev · 2026-08-18 14:56
svengonna implement that on the linux side and then push it later today
#asahi-dev · 2026-08-18 14:56
svenokay, i think i got the cable vse nonsense down now
#asahi-dev · 2026-08-17 19:56
svenhttps://lore.kernel.org/asahi/20260817-b4-tbt-fixes-v1-0-eded2461f5fc@kernel.org/ hopefully that's all the fixes in the core i need
#asahi-dev · 2026-08-17 17:00
svenOkay… I’m just gonna go ahead and reverse engineer that cable vse now. can’t really make sense of it otherwise *sigh*
#asahi-dev · 2026-08-17 12:26
svenwhat made the gpu one so painful? lots of rust bindings upstreamed?
#asahi-dev · 2026-08-17 12:26
svenand here i thought thunderbolt was bad already
#asahi-dev · 2026-08-17 09:55
svendon't jinx it! :P
#asahi-dev · 2026-08-17 09:53
sven🙃
#asahi-dev · 2026-08-17 07:44
sveni think so far the interface was just very stable and we suspected it's done by a different team who cares about backwards/forwards compatibility
#asahi-dev · 2026-08-17 07:42
sveni think so
#asahi-dev · 2026-08-17 07:29
sven:(
#asahi-dev · 2026-08-16 19:47
sven5 fixes for a single commit by now 🙃
#asahi-dev · 2026-08-16 19:47
svens/dcp/thunderbolt/ and s/crashing/hanging forever/ and that were my last days :D
#asahi-dev · 2026-08-16 11:59
svenjust need to figure out that cable status thing now and then this should be ready to submit after -rc1 is out
#asahi-dev · 2026-08-16 11:58
svenand i wrote dt-bindings \o/
#asahi-dev · 2026-08-16 11:57
svenbut i think i finally have sane fixes for the issues when plugging in devices now
#asahi-dev · 2026-08-16 11:57
svenhates thunderbolt
#asahi-dev · 2026-08-16 10:03
sventhat sounds reasonable
#asahi-dev · 2026-08-16 09:36
sven*just like
#asahi-dev · 2026-08-16 09:36
svenjust the tbt review, but i'm more and more convinced that my nhi is a child of the acio block is actually a good description of this hardware. all MMIO is in a 16 MiB range anyway
#asahi-dev · 2026-08-16 09:35
svenoh, don't get me wrong. i'm not against that, i'm just saying the review is gonna be fun
#asahi-dev · 2026-08-16 09:34
svenor a binding that takes both variants but ugh..
#asahi-dev · 2026-08-16 09:34
svenprobably needs a new compatible either way
#asahi-dev · 2026-08-16 09:32
svenchadmed: i can already see the "bindings should not be influenced by the driver" review :/
#asahi-dev · 2026-08-16 08:40
svennice!
#asahi-dev · 2026-08-15 18:41
svencould be something like clock gating vs. power gating but who knows
#asahi-dev · 2026-08-15 18:40
sveni don't really care about naming, but deep wfi has always been very confusing to me
#asahi-dev · 2026-08-15 18:36
svensemi-retention wfi? :P
#asahi-dev · 2026-08-15 18:32
svenyeah, and that's where my question came "is there a different between "wfi that jumps back to RVBAR" and "wfi that results in full cluster shutdown"?" came from because i'm not sure
#asahi-dev · 2026-08-15 18:31
sventhat's why i'm asking if there's a difference or if deep = false is just "enter shutdown wfi but don't set the cluster shutdown reg", i.e. some weird inbetween state
#asahi-dev · 2026-08-15 18:30
svendeep = false -> ends up at RVBAR as well
#asahi-dev · 2026-08-15 18:29
svenchaos_princess: i'm talking about the difference between deep=true/false here https://github.com/AsahiLinux/m1n1/blob/88a98213d55f2cbd69844762c3171b39c0cd0bf9/src/utils.c#L249
#asahi-dev · 2026-08-15 18:27
sven*difference
#asahi-dev · 2026-08-15 18:27
svenis there a different between "wfi that jumps back to RVBAR" and "wfi that results in full cluster shutdown"?
#asahi-dev · 2026-08-15 18:26
sven<yuka> If 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 <-- let's maybe do just that :D
#asahi-dev · 2026-08-15 18:24
svenmaybe another confusion of terminology and that was from before the cpuidle driver
#asahi-dev · 2026-08-15 18:24
sven"/* Not available until CPU deep sleep is implemented */"
#asahi-dev · 2026-08-15 18:23
svenhttps://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm64/boot/dts/apple/t8103.dtsi#n283 hmmm
#asahi-dev · 2026-08-15 18:23
svenyup, agreed
#asahi-dev · 2026-08-15 18:23
sventhat sounds like what i thought required actual power off
#asahi-dev · 2026-08-15 18:22
svenbut good to know
#asahi-dev · 2026-08-15 18:22
svenhuh, i was somehow convinced that we couldn't boost to the highest pstate yet
#asahi-dev · 2026-08-15 18:20
svenah, i thought that wasn't enough
#asahi-dev · 2026-08-15 18:19
sveni thought for boosting to the highest state the other cores had to be actually powered off. but i could be wrong, never looked into that in details
#asahi-dev · 2026-08-15 18:18
svenand for boosting you need more, don't you?
#asahi-dev · 2026-08-15 18:17
svenboth chaos and me tried and while we can get the cores to go into deep sleep / poweroff we can't wake from the state again if we put all cores into it
#asahi-dev · 2026-08-15 18:16
svenonce we actually get that working on m1-m3 we can try filing a radar again and see what happens
#asahi-dev · 2026-08-15 18:16
sven*modify

plus ›