#asahi-dev · 2026-08-17 07:46
JamesCalligeros[m]and why create_dfb was inexplicably failing#asahi-dev · 2026-08-17 07:46
JamesCalligeros[m]that might actually explain the new apple-shaped hole on surface 0 that i was seeing#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:32
jannaui.e. the os specific part, i.e. iboot and dcp fw are version matched#asahi-dev · 2026-08-17 07:31
jannauisn't dcp firmware loaded by iboot2#asahi-dev · 2026-08-17 07:31
yukayeah#asahi-dev · 2026-08-17 07:31
yuka> display: failed to initialize DCP iBoot interface#asahi-dev · 2026-08-17 07:31
jannauyuka: iboot never handled dptx. on M1* with macOS 11 (which initialised the desktop HDMI port) it was handled in the dcp firmware. It wasn't that different from how the laptops worked#asahi-dev · 2026-08-17 07:30
JamesCalligeros[m]i would have thought that would have to remain stable given that i can theoretically install whichever macos version i want and iboot has to just cop it#asahi-dev · 2026-08-17 07:29
JamesCalligeros[m]did they break the iboot interface?#asahi-dev · 2026-08-17 07:23
yukabrb watching https://www.youtube.com/watch?v=Ka8Lmkdf_aY#asahi-dev · 2026-08-17 07:18
yukathat's probably a bit more annoying to reverse, since iboot no longer does this?#asahi-dev · 2026-08-17 07:17
yukaAh, I see it has a dcp_ib_init#asahi-dev · 2026-08-17 07:16
yukahow does the dcp-dptx thing on work on the Mac mini? Is the resulting framebuffer also borderline unusable without gpu?#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 13:09
chadmedi was mostly trying to stop dcp from crashing this week :P #asahi-dev · 2026-08-16 13:08
chadmedforcing everything to be interchange and then running cts? i havent done that yet, was planning to do it next weekend#asahi-dev · 2026-08-16 12:59
jannauhave you already done the torture tests alyssa proposed in mesa against vk/opengl CTS?#asahi-dev · 2026-08-16 12:18
chadmedre interchange, should i just submit the format modifier to lkml? ive tested https://github.com/chadmed/linux/tree/dcp/interchange with https://gitlab.freedesktop.org/chadmed/mesa/-/tree/asahi/interchange on t8103, t8112, t6000 and t6021 and it all seems to work fine#asahi-dev · 2026-08-16 12:05
chadmedhttps://github.com/AsahiLinux/linux/pull/569#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 11:06
chadmedhuh, yeah that worked#asahi-dev · 2026-08-16 10:56
jannauI don't think this is too ugly and should make the shared-gpio-proxy work#asahi-dev · 2026-08-16 10:55
jannaujust change the flags in devm_gpiod_get_optional to GPIOD_OUT_LOW and potentionally set it high earlier if something expects to interact with it before tas27*_codec_probe.#asahi-dev · 2026-08-16 10:50
chadmed(and exactly what the shared reset api is for)#asahi-dev · 2026-08-16 10:49
chadmedwhich makes this work, but it seems like this is exactly what they _dont_ want it to do :P #asahi-dev · 2026-08-16 10:49
chadmedi added a hack to reset the vote state tracking and simply assert the line when any consumer wants it asserted#asahi-dev · 2026-08-16 10:47
chadmedwith this now the chips dont come out of shutdown until the last codec asserts the line#asahi-dev · 2026-08-16 10:46
chadmedthis is what i was complaining about the other day #asahi-dev · 2026-08-16 10:46
chadmedit was changed :) #asahi-dev · 2026-08-16 10:46
chadmedb30973e8c3920ddfa9255a959b19057515b4e5e8#asahi-dev · 2026-08-16 10:45
jannau"treat the output-high value as a reference counted, logical "GPIO enabled" setting, meaning: the GPIO value is set to high when the first user requests it to be high and back to low once the last user stops "voting" for high."#asahi-dev · 2026-08-16 10:44
jannaufrom the description of e992d54c6f970b382ffeacd7c88f68b94a3c6caf the shared gpio proxy should work#asahi-dev · 2026-08-16 10:44
chadmedi wonder if we can extend the api to add variants that look for shutdown-gpios instead of reset-gpios#asahi-dev · 2026-08-16 10:42
chadmedthe shared reset controller api really seems like the right tool for this particular job based on krzystof's talk but obviously we are kinda cooked here with the dt binding#asahi-dev · 2026-08-16 10:42
chadmedthe shared gpio thing will not work either without changes as it requires all consumers to vote on any change now, not just on deassert#asahi-dev · 2026-08-16 10:40
jannauif avaoidable we should not use a reset controller for shutdown#asahi-dev · 2026-08-16 10:38
chadmedyeah, we'd need to use named resets which is now back to changing the binding#asahi-dev · 2026-08-16 10:37
jannauyes, we want shutdown-gpios and not reset-gpios. I don't think the reset controler will work for this#asahi-dev · 2026-08-16 10:36
chadmedso im still not sure how we handle this gracefully. if the driver expects to actually reset the chip in the tas27xx_reset then deasserting the line while another codec is holding it high will not actually reset the chip that needs to be reset#asahi-dev · 2026-08-16 10:35
chadmedall the pm ops use the shutdown gpio#asahi-dev · 2026-08-16 10:35
chadmedthe actual reset path pulses the reset line, which should never occur on a shared line#asahi-dev · 2026-08-16 10:34
chadmedi wonder if the intent here was to deal with situations like this#asahi-dev · 2026-08-16 10:20
jannauthe tas27xx dt-bindings example even uses the gpio pin for reset and shutdown