#asahi-dev · 2025-05-30 13:30
svenlol, i don't know why but adding minItems and maxItems to iommus in apple,dwc3.yaml seems to fix that issue#asahi-dev · 2025-05-30 12:20
svenand added ports to the atcphy binding like that qcom phy you found has#asahi-dev · 2025-05-30 12:20
svenjannau: i've dropped the drm hotplug thing for now fwiw#asahi-dev · 2025-05-30 12:19
svenjust need to ask robh about that snps,dwc3 issue because I don't understand what the validator does, write some commit descriptions, maybe reorder some commits and write a cover letter#asahi-dev · 2025-05-30 12:19
sventhat's the plan after -rc1 :D#asahi-dev · 2025-05-30 12:18
svenwhere just work means everything is still powered on but that's good enough for now#asahi-dev · 2025-05-30 12:18
svenso, uh, i just went through a suspend -> resume cycle with atcphy it seems to just work I guess?#asahi-dev · 2025-05-30 10:36
svenyeah#asahi-dev · 2025-05-30 10:35
sveni wonder if this is just a bug inside the validator#asahi-dev · 2025-05-30 10:35
svenokay, allowing two iommus inside snps,dwc3.yaml seems to fix it#asahi-dev · 2025-05-30 10:26
sveni guess because of the snps,dwc3 compatible :/#asahi-dev · 2025-05-30 10:25
svenI wonder why it even tries to validate against snps,dwc3.yaml. I only include snps,dwc3-common.yaml##asahi-dev · 2025-05-30 10:09
svenso that's what I get even with the select stanza#asahi-dev · 2025-05-30 10:09
sven from schema $id: http://devicetree.org/schemas/usb/snps,dwc3.yaml##asahi-dev · 2025-05-30 10:09
sven from schema $id: http://devicetree.org/schemas/usb/snps,dwc3.yaml##asahi-dev · 2025-05-30 10:09
svenhome/speter/linux/arch/arm64/boot/dts/apple/t8103-j457.dtb: usb@502280000: Unevaluated properties are not allowed ('iommus' was unexpected)#asahi-dev · 2025-05-30 10:09
svenhome/speter/linux/arch/arm64/boot/dts/apple/t8103-j457.dtb: usb@502280000: iommus: [[104, 0], [105, 1]] is too long#asahi-dev · 2025-05-30 10:09
svenmeh#asahi-dev · 2025-05-30 10:09
sven from schema $id: http://devicetree.org/schemas/usb/snps,dwc3.yaml##asahi-dev · 2025-05-30 10:09
sven from schema $id: http://devicetree.org/schemas/usb/snps,dwc3.yaml##asahi-dev · 2025-05-30 09:48
svenmaybe. i removed that snps compatible for now because I didn't want to deal with that :D#asahi-dev · 2025-05-30 09:41
sveni can give it another try and see if i can fix it. iirc it was because the apple ones needs two iommus and that clashed with snps,dwc3-common.yaml#asahi-dev · 2025-05-30 09:40
svencouldn't get dtbs_check to pass with that one included :/#asahi-dev · 2025-05-30 09:03
sveni think that's what i meant, dynamic debug sounds familiar #asahi-dev · 2025-05-30 09:02
svenor maybe it was the command line#asahi-dev · 2025-05-30 09:01
sventhere's some way to enable them just for rtkit with a write to some debugfs(?) node iirc#asahi-dev · 2025-05-30 09:00
svenwe can just turn dev_info into dev_dbg for syslog messages#asahi-dev · 2025-05-30 06:36
svenI also don’t think it’s even related to PAN#asahi-dev · 2025-05-30 06:33
svenwe have multiple ways to work around it but that’s not the point #asahi-dev · 2025-05-29 21:58
svenwhat I don't understand is why increasing DUMMY_STACK makes the issue disappear as well#asahi-dev · 2025-05-29 21:56
svenand then it never stored/loaded lr from the stack#asahi-dev · 2025-05-29 21:56
sven*inlined#asahi-dev · 2025-05-29 21:56
sveni'll have to try again but I think what happened is that supports_pan was somehow inline when I added "too much debugging" to mmu_setup_secondary#asahi-dev · 2025-05-29 21:42
sventrue#asahi-dev · 2025-05-29 21:40
svenand adding just slightly too much debugging made the exception disappear as well#asahi-dev · 2025-05-29 21:40
svenI didn't even find any instruction that would write 0x2000000 somewhere and would make sense in that context when I checked a few weeks ago#asahi-dev · 2025-05-29 21:31
svenif this really is some timing issue i'm not sure even a SWD debugger for host m1n1 would help debugging this#asahi-dev · 2025-05-29 21:30
sventhe truly weird part is that sometimes bringing up core 1 works and then it fails at the same place for core 2#asahi-dev · 2025-05-29 20:38
sven 00125f7c fd 7b bf a9 stp x29,x30,[sp, #local_10]! <-- so that's x29 and lr before it branches to supports_pan. by the time it returns both seem to be corrupted#asahi-dev · 2025-05-29 20:18
svenjannau: so i'm even more confused by that mmu_setup_secondary abort. i also see a different address inside m1n1 for x29 vs sp which looks reasonable. maybe x29 gets corrupted as well? but i dont see how :/#asahi-dev · 2025-05-29 20:17
svene.g. the device one just sets the right bit in DWC3_GCTL_PRTCAP#asahi-dev · 2025-05-29 20:16
svenon m1+ the dwc3 tunables in the ADT are just documented writes to the normal dwc3 regs iirc#asahi-dev · 2025-05-29 15:23
sven*them #asahi-dev · 2025-05-29 15:23
svenatcphy needs then because what Apple calls „tunables“ are there is in reality 10% tunables and 90% init sequence they didn’t want to put into the atcphy kext for whatever reason #asahi-dev · 2025-05-29 14:24
svenhttps://git.kernel.org/pub/scm/linux/kernel/git/sven/linux.git/log/?h=wip/atcphy and https://github.com/AsahiLinux/m1n1/pull/469 handles fuses as if they were another tunable and I think I like it that way#asahi-dev · 2025-05-29 10:15
svenlol#asahi-dev · 2025-05-27 21:49
svenso we may still corrupt the stack but just not notice #asahi-dev · 2025-05-27 21:49
sventhe difference between gcc and clang was that clang had that additional function call inside mmu_setup_secondary while gcc inline that function instead iirc