#
…

2026-08-16

00:13pb17 has quit [Ping timeout: 480 seconds]
00:16pb17 has joined #asahi-dev
01:04___nick___ has quit []
01:06jnn has joined #asahi-dev
01:07___nick___ has joined #asahi-dev
01:08___nick___ has quit []
01:10jn has quit [Ping timeout: 480 seconds]
01:10___nick___ has joined #asahi-dev
01:52Werner[m] has joined #asahi-dev
02:00yurix has quit [Remote host closed the connection]
02:00yurix has joined #asahi-dev
02:00ciara has quit [Remote host closed the connection]
02:12ciara has joined #asahi-dev
02:43tobhe has joined #asahi-dev
02:47AlohaHenry has joined #asahi-dev
02:50tobhe_ has quit [Ping timeout: 480 seconds]
03:17nora_ has joined #asahi-dev
03:19nora has quit [Ping timeout: 480 seconds]
03:39AlohaHenry has quit [Quit: AlohaHenry]
05:27k70 has quit [Quit: gone]
05:27k70 has joined #asahi-dev
06:01bgb has quit [Remote host closed the connection]
06:02bgb has joined #asahi-dev
06:15nela has quit [Quit: Ping timeout (120 seconds)]
06:16nela has joined #asahi-dev
06:22nela has quit [Quit: Ping timeout (120 seconds)]
06:22nela has joined #asahi-dev
06:40rosalyntg_ has joined #asahi-dev
06:40rosalyntg has quit [Read error: Connection reset by peer]
06:45pb17 has quit [Ping timeout: 480 seconds]
06:50pb17 has joined #asahi-dev
07:14chadmed has quit [Quit: Konversation terminated!]
07:59chadmed has joined #asahi-dev
08:37yukayay, I found a tz_regs mapping for t8140/t6040 which makes sense
08:41yukathis was my previous attempt of staring at it: https://termbin.com/eiitlb
08:42yukaI noticed on t6031, the slot between 2 and 4 has range 0x10000000-0x10000000 and is _disabled_
08:42yukaand this makes sense if the stride is 4, then you read it as columns
08:42yukafrom top to bottom: start, end, unused/unk, enable
08:44yukaand then it gives the following entries: [(0x101e6e30-0x101e8ec7, enabled), (0x10000000-0x10000000, disabled), (0x101f1a5c-0x101ffc5b, enabled), (0x10000000-0x10000000, disabled)]
09:05yukatrying to understand the T6000_DCS_OFFSET and T6000_DCS_STRIDE
09:05jannauchaos_princess: re dcp carveouts, matching segment-ranges against carveout-memory-map/region-id-*. we started with matching pre-existing mapped regions in dart-{dcp,disp}* against carveouts but if I'm not mistaken it's just the annotated segments
09:07chaos_princess(trying to throw the dcp driver on the t6031 and see what breaks)
09:07jannauwe probably can switch to parsing segment-ranges
09:08yukaAs I read this, the 4 DCS instances on T6000 should be at 0x200000, 0x300000, 0x400000, 0x500000
09:08yukabut 0x300000 gives me an SError
09:09yukano, nevermind, question still stands
09:14yukastride of 0x200000 would make more sense, since all of 0x200000, 0x400000, 0x600000, 0x800000 are readable
09:18jannauT6031_DCS_STRIDE is 0x200000. are you testing on T6000? maybe it's just wrong since it is never used
09:18yukaYes, I'm testing on T6000
09:23yukaOK nice, T8132 DCS are in the same locations as T6031
09:25chadmedi dont think theres a good solution to the codec shared gpio problem. the best(tm) solution would be to use the new-ish shared reset controller api which is specifically for this
09:25chadmedhowever that will require binding changes
09:26chadmedafaict we are the only user of both tas2764 and tas2770 so maybe thats not a problem?
09:32jannauyuka: https://www.youtube.com/watch?v=GUSFOP_lFmA or the "Bringing up Asahi Linux on the M1 Pro" series might be relevant. Those are just before the initial src/mcc.c commit
09:32svenchadmed: i can already see the "bindings should not be influenced by the driver" review :/
09:33jannauchadmed: I wouldn't be sure of that given that both bindings are written by TI
09:33JamesCalligeros[m]I grepped the compatible and didnt find anything in tree but yeah theres probably some board somewhere
09:34svenprobably needs a new compatible either way
09:34svenor a binding that takes both variants but ugh..
09:34JamesCalligeros[m]Theres really no other good solution than using this api
09:35svenoh, don't get me wrong. i'm not against that, i'm just saying the review is gonna be fun
09:35JamesCalligeros[m]Id rather not of_machine_is_compatible a bunch of stuff in the driver either
09:35JamesCalligeros[m]Seems like the nuclear option
09:36svenjust 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
09:36sven*just like
09:38marvin24 has joined #asahi-dev
09:42jannaubut why would using the shared reset controller require binding changes? I thought it was designed to work with the existing "reset-gpios" without changes
09:51JamesCalligeros[m]The driver already uses reset-gpios unconditionally for an actual chip reset line. We would have to add reset-names and call ours “sdz” or something
09:51JamesCalligeros[m]It’s a different pin to the chip’s actual reset
09:52JamesCalligeros[m]Perhaps the driver can check if the named reset exists and fall back to the old behaviour if it doesnt
09:56hardy94 has joined #asahi-dev
10:01Acelogic has joined #asahi-dev
10:03sventhat sounds reasonable
10:04jannaulooking at the tas2764/tas2770 data sheets I don't see a reset pin, just sdz and power supply oins
10:08Acelogic_ has quit [Ping timeout: 480 seconds]
10:09JamesCalligeros[m]Huh, i cant remember why we treat the fake regulator path differently then
10:10JamesCalligeros[m]In that case we might be able to use the magic reset-gpios proxy after all
10:10JamesCalligeros[m]Ill check when i get home
10:10jannauI think we just have to change the drivers from using the reset gpio pin directly via gpiod to the reset controller framework
10:12JamesCalligeros[m]Yeah, hopefully unconditionally getting the reset as shared doesnt introduce much overhead or cause problems when it’s not actually shared
10:14jannauhuh, both drivers also use shutdown-gpios and map this to sdz
10:14JamesCalligeros[m]Yeah thats why i was confused
10:20jannauthe tas27xx dt-bindings example even uses the gpio pin for reset and shutdown
10:31chadmed has quit [Quit: Konversation terminated!]
10:32chadmed has joined #asahi-dev
10:34chadmedi wonder if the intent here was to deal with situations like this
10:35chadmedthe actual reset path pulses the reset line, which should never occur on a shared line
10:35chadmedall the pm ops use the shutdown gpio
10:36chadmedso 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
10:37jannauyes, we want shutdown-gpios and not reset-gpios. I don't think the reset controler will work for this
10:38chadmedyeah, we'd need to use named resets which is now back to changing the binding
10:40jannauif avaoidable we should not use a reset controller for shutdown
10:42chadmedthe shared gpio thing will not work either without changes as it requires all consumers to vote on any change now, not just on deassert
10:42chadmedthe 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
10:44chadmedi wonder if we can extend the api to add variants that look for shutdown-gpios instead of reset-gpios
10:44jannaufrom the description of e992d54c6f970b382ffeacd7c88f68b94a3c6caf the shared gpio proxy should work
10:45jannau"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."
10:46chadmedb30973e8c3920ddfa9255a959b19057515b4e5e8
10:46chadmedit was changed :)
10:46chadmedthis is what i was complaining about the other day
10:47chadmedwith this now the chips dont come out of shutdown until the last codec asserts the line
10:49chadmedi added a hack to reset the vote state tracking and simply assert the line when any consumer wants it asserted
10:49chadmedwhich makes this work, but it seems like this is exactly what they _dont_ want it to do :P
10:50chadmed(and exactly what the shared reset api is for)
10:55jannaujust 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.
10:56jannauI don't think this is too ugly and should make the shared-gpio-proxy work
11:04chadmed has quit [Quit: Konversation terminated!]
11:06chadmed has joined #asahi-dev
11:06chadmedhuh, yeah that worked
11:57* svenhates thunderbolt
11:57svenbut i think i finally have sane fixes for the issues when plugging in devices now
11:58svenand i wrote dt-bindings \o/
11:59svenjust need to figure out that cable status thing now and then this should be ready to submit after -rc1 is out
11:59pb17 has quit [Remote host closed the connection]
12:00pb17 has joined #asahi-dev
12:13hardy94 has quit [Remote host closed the connection]
12:18chadmedre 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
12:47foltz5 has quit [Ping timeout: 480 seconds]
12:52foltz5 has joined #asahi-dev
12:59jannauhave you already done the torture tests alyssa proposed in mesa against vk/opengl CTS?
13:08chadmedforcing everything to be interchange and then running cts? i havent done that yet, was planning to do it next weekend
13:09chadmedi was mostly trying to stop dcp from crashing this week :P
13:22hardy94 has joined #asahi-dev
13:43hardy94 has quit [Remote host closed the connection]
13:52hdbngr has joined #asahi-dev
14:06hdbngr has quit [Ping timeout: 480 seconds]
14:07hdbngr has joined #asahi-dev
14:18hdbngr has quit [Ping timeout: 480 seconds]
14:38barusu has quit [Ping timeout: 480 seconds]
14:57hdbngr has joined #asahi-dev
15:06hdbngr has quit [Ping timeout: 480 seconds]
15:52hdbngr has joined #asahi-dev
15:58hdbngr has quit [Remote host closed the connection]
15:58hdbngr has joined #asahi-dev
16:00bgb has quit [Remote host closed the connection]
16:00bgb has joined #asahi-dev
16:07hdbngr has quit [Ping timeout: 480 seconds]
16:09marvin24 has quit [Ping timeout: 480 seconds]
16:13hdbngr has joined #asahi-dev
16:25hdbngr has quit [Ping timeout: 480 seconds]
16:45hdbngr has joined #asahi-dev
16:46__nick__ has joined #asahi-dev
16:49___nick___ has quit [Ping timeout: 480 seconds]
16:53violette has quit [Quit: ZNC 1.10.1 - https://znc.in]
16:53hdbngr has quit [Ping timeout: 480 seconds]
16:55violette has joined #asahi-dev
16:57hdbngr has joined #asahi-dev
17:02mixi has quit [Quit: quit]
17:02mixi has joined #asahi-dev
17:03elvishjerricco has quit [Ping timeout: 480 seconds]
17:04pb17 has quit [Ping timeout: 480 seconds]
17:11hdbngr has quit [Remote host closed the connection]
17:11hdbngr has joined #asahi-dev
17:13pb17 has joined #asahi-dev
17:23hdbngr has quit [Ping timeout: 480 seconds]
17:31hdbngr has joined #asahi-dev
17:39hdbngr has quit [Ping timeout: 480 seconds]
17:47hdbngr has joined #asahi-dev
17:57hdbngr has quit [Ping timeout: 480 seconds]
18:00hdbngr has joined #asahi-dev
18:08hdbngr has quit [Ping timeout: 480 seconds]
18:13donaldh has quit [Read error: Connection reset by peer]
18:27pb17 has quit [Ping timeout: 480 seconds]
18:32hdbngr has joined #asahi-dev
18:34pb17 has joined #asahi-dev
18:41hdbngr has quit [Ping timeout: 480 seconds]
19:01hdbngr has joined #asahi-dev
19:09hdbngr has quit [Ping timeout: 480 seconds]
19:12elvishjerricco has joined #asahi-dev
19:23hdbngr has joined #asahi-dev
19:31hdbngr has quit [Ping timeout: 480 seconds]
19:40violette has quit [Quit: ZNC 1.10.1 - https://znc.in]
19:42violette has joined #asahi-dev
19:44violette has quit []
19:45violette has joined #asahi-dev
19:45WindowPain8 has joined #asahi-dev
19:47svens/dcp/thunderbolt/ and s/crashing/hanging forever/ and that were my last days :D
19:47sven5 fixes for a single commit by now 🙃
19:48hdbngr has joined #asahi-dev
19:51WindowPain has quit [Ping timeout: 480 seconds]
19:51WindowPain8 is now known as WindowPain
19:57hdbngr has quit [Ping timeout: 480 seconds]
20:02hdbngr has joined #asahi-dev
20:06__nick__ has quit [Remote host closed the connection]
20:08bgb has quit [Remote host closed the connection]
20:08bgb has joined #asahi-dev
20:08barusu has joined #asahi-dev
20:10hdbngr has quit [Ping timeout: 480 seconds]
20:14barusu has quit [Remote host closed the connection]
20:15barusu has joined #asahi-dev
20:27pb17 has quit [Ping timeout: 480 seconds]
20:30pb17 has joined #asahi-dev
20:41hdbngr has joined #asahi-dev
20:52violette has quit [Quit: ZNC 1.10.1 - https://znc.in]
20:56rany has quit [Remote host closed the connection]
21:02hdbngr has quit [Ping timeout: 480 seconds]
21:03hdbngr has joined #asahi-dev
21:03rany has joined #asahi-dev
21:11hdbngr has quit [Ping timeout: 480 seconds]
21:21rany has quit [Remote host closed the connection]
21:21Yushi has quit [Remote host closed the connection]
21:21rany has joined #asahi-dev
21:23Yushi has joined #asahi-dev
21:32barusu has quit [Remote host closed the connection]
21:33barusu has joined #asahi-dev
21:34bgb has quit [Remote host closed the connection]
21:35bgb has joined #asahi-dev
22:07hdbngr has joined #asahi-dev
22:15hdbngr has quit [Ping timeout: 480 seconds]
22:16jsk_ has joined #asahi-dev
22:18cy8aer has quit [Remote host closed the connection]
22:19jsk has quit [Ping timeout: 480 seconds]
22:19cy8aer has joined #asahi-dev
22:20jsk_ is now known as jsk
23:14bgb has quit [Remote host closed the connection]
23:16bgb has joined #asahi-dev
23:42pb17 has quit [Ping timeout: 480 seconds]
23:56pb17 has joined #asahi-dev
…