#asahi-dev · 2026-09-11 08:23
jobe[m]hello! some days ago my observation posted in #asahi was left uncommented: on a j613 (M3) with the latest EXPERT=1 official-release u-boot/m1n1, I always receive "0 usb storage devices found" after several restarts (and "usb reset") trying both usb-ports and five different brands of usb-c-flashdrives (these immutable debian-live-bananas work being used on M1/M2).. any hints?#asahi-dev · 2026-09-11 08:18
chadmedwe've had a couple of reports of it being audible over the headphone jack too#asahi-dev · 2026-09-11 08:17
chadmedyou think its coils? i recall hearing it from both sides of the machine #asahi-dev · 2026-09-11 08:17
sofusi feel like the sound is loudest near the 8 and 9 keys#asahi-dev · 2026-09-11 08:17
sofuschadmed: how did you verify the sound came from the speakers?#asahi-dev · 2026-09-11 08:09
sofusthe timeouts could be something power related to, its seems it only happens after some time idle#asahi-dev · 2026-09-11 08:03
chadmeddoing certain things on the gpu also causes annoying noises so im thinking we're not setting up some power management thing properly#asahi-dev · 2026-09-11 08:03
chadmedi never figured out the squealing through the speakers, it seems to be model-dependent and all the time. doing stuff over wifi only makes it worse#asahi-dev · 2026-09-11 08:02
chadmedcould just be brcmfmac brcmfmacing#asahi-dev · 2026-09-11 07:58
sofustime to debug my screaming wifi. I also have an issue with requests timing out, but i guess that could also be a configuration issue#asahi-dev · 2026-09-11 07:49
chadmedthis is why EXPERT=1 :P #asahi-dev · 2026-09-11 07:49
sofusi did not understand where the interrupts-extended value came from, should have started there :p#asahi-dev · 2026-09-11 07:49
chadmedlmao thatd do it #asahi-dev · 2026-09-11 07:48
sofusdt was wrong, https://github.com/AsahiLinux/linux/pull/612#asahi-dev · 2026-09-10 21:14
sofusis this a stupid test? Im trying to see if i can stop the irq's, but nothing seems to work https://pastebin.com/Zbx5t1i0#asahi-dev · 2026-09-10 20:37
JamesCalligeros[m]Likely power management related#asahi-dev · 2026-09-10 20:36
JamesCalligeros[m]Ohhhhhh yeah no thats just RF interference#asahi-dev · 2026-09-10 19:38
sofusthere is also a similar sound when im installing stuff with wifi#asahi-dev · 2026-09-10 19:27
sofusat some point it detects a Unplug event, and after that both tip and ring state are 0#asahi-dev · 2026-09-10 18:08
sofuschadmed: im a bit confused, im not pluggin anything in? The comment at the top indicates the interrupts should be cleared#asahi-dev · 2026-09-10 13:06
myriathanks jannau!#asahi-dev · 2026-09-10 12:45
jannau`git grep "#define MIDR_PART_"` in m1n1#asahi-dev · 2026-09-10 12:44
chadmediirc this was pretty much the only way to prevent spurious misdetections of headset vs headphones #asahi-dev · 2026-09-10 12:44
chadmedsofus: https://github.com/AsahiLinux/linux/blob/asahi-wip/sound/soc/codecs/cs42l84.c#L845 we might be trying to be a little too clever here #asahi-dev · 2026-09-10 12:39
myriahey, does anyone have MIDR_EL1 values for m3? I have the max variants, but from the looks of M1/M2 the base/Pro/Ultra might have different values?#asahi-dev · 2026-09-10 12:17
sofushttps://pastebin.com/PTyt5rSz#asahi-dev · 2026-09-10 12:17
sofusi traced my "talking" headphone jack, it looks like the irq is never cleared propperly#asahi-dev · 2026-09-10 10:56
jannauthose are the only 5 regs I've seen in the trace and their naming odesn't look outlandish. I guess dpin will become some sort of HPD connector / bridge#asahi-dev · 2026-09-10 10:46
sventhough i don't think i looked for an MMIO reg that contains the protocol adapter index#asahi-dev · 2026-09-10 10:46
svenhttps://f.svpe.de/d09f1fa677f4a843e9c9eb42840f8992861131d2474ec1c200760a5c7fd9c13f_dpin.h found it#asahi-dev · 2026-09-10 09:04
svenyeah, I remember it being very simple #asahi-dev · 2026-09-10 08:57
jannausven: atc-dpin is very small, only 5 32-bit registers and none look like they would contain the thunderbolt adapter id. 0x00 - 0x0c are read/write and 0x10 appears to be a status reg#asahi-dev · 2026-09-10 08:40
jannauI haven't found any other changes touching atc-dpin.c #asahi-dev · 2026-09-10 07:49
svenjust noticed as well :D#asahi-dev · 2026-09-10 07:49
svenlol#asahi-dev · 2026-09-10 07:49
jannauwithout code though#asahi-dev · 2026-09-10 07:48
sveni knew it had to be somewhere#asahi-dev · 2026-09-10 07:48
svenhah, thanks!#asahi-dev · 2026-09-10 07:48
jannausven: atcphy-20230219 on github has "phy: apple: Add DPIN"#asahi-dev · 2026-09-10 07:27
svenit might’ve been paste because I looked at old branches and didn’t see it either #asahi-dev · 2026-09-10 07:26
svenno idea unfortunately #asahi-dev · 2026-09-10 07:26
jannaudo you remember how you shared the code? via paste or git branch. in the second case I likely still have it although the question is where#asahi-dev · 2026-09-10 07:25
jannauI have a faint recollection but I didn't notice it when I was looking for old thunderbolt branches to see if we had it working on M1 Max#asahi-dev · 2026-09-10 07:22
svenmainly curious if the protocol adapter id is in some MMIO or if we need it in the dt instead #asahi-dev · 2026-09-10 07:21
svenjannau: do you still have the dpin code I wrote ages ago for dp tunneling somewhere by chance? I don’t remember if it worked but I do remember reverse engineering it #asahi-dev · 2026-09-10 06:01
nickchanimmediately obvious from the amount of changes inside target/arm/tcg#asahi-dev · 2026-09-10 06:00
svenhuh, I thought it was hv.framework only #asahi-dev · 2026-09-10 06:00
nickchan-qemu's emulation jit#asahi-dev · 2026-09-10 06:00
nickchan-not some hv.framework stuff#asahi-dev · 2026-09-10 06:00
sventcg?