#asahi-dev · 2026-08-16 10:14
JamesCalligeros[m]Yeah thats why i was confused#asahi-dev · 2026-08-16 10:14
jannauhuh, both drivers also use shutdown-gpios and map this to sdz#asahi-dev · 2026-08-16 10:12
JamesCalligeros[m]Yeah, hopefully unconditionally getting the reset as shared doesnt introduce much overhead or cause problems when it’s not actually shared#asahi-dev · 2026-08-16 10:10
jannauI think we just have to change the drivers from using the reset gpio pin directly via gpiod to the reset controller framework#asahi-dev · 2026-08-16 10:10
JamesCalligeros[m]Ill check when i get home#asahi-dev · 2026-08-16 10:10
JamesCalligeros[m]In that case we might be able to use the magic reset-gpios proxy after all#asahi-dev · 2026-08-16 10:09
JamesCalligeros[m]Huh, i cant remember why we treat the fake regulator path differently then#asahi-dev · 2026-08-16 10:04
jannaulooking at the tas2764/tas2770 data sheets I don't see a reset pin, just sdz and power supply oins#asahi-dev · 2026-08-16 10:03
sventhat sounds reasonable #asahi-dev · 2026-08-16 09:52
JamesCalligeros[m]Perhaps the driver can check if the named reset exists and fall back to the old behaviour if it doesnt#asahi-dev · 2026-08-16 09:51
JamesCalligeros[m]It’s a different pin to the chip’s actual reset#asahi-dev · 2026-08-16 09:51
JamesCalligeros[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#asahi-dev · 2026-08-16 09:42
jannaubut why would using the shared reset controller require binding changes? I thought it was designed to work with the existing "reset-gpios" without changes#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
JamesCalligeros[m]Seems like the nuclear option#asahi-dev · 2026-08-16 09:35
JamesCalligeros[m]Id rather not of_machine_is_compatible a bunch of stuff in the driver either#asahi-dev · 2026-08-16 09:35
JamesCalligeros[m]Yeah :/#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
JamesCalligeros[m]Theres really no other good solution than using this api#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:33
JamesCalligeros[m]I grepped the compatible and didnt find anything in tree but yeah theres probably some board somewhere#asahi-dev · 2026-08-16 09:33
jannauchadmed: I wouldn't be sure of that given that both bindings are written by TI#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 09:32
jannauyuka: 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#asahi-dev · 2026-08-16 09:26
chadmedafaict we are the only user of both tas2764 and tas2770 so maybe thats not a problem?#asahi-dev · 2026-08-16 09:25
chadmedhowever that will require binding changes#asahi-dev · 2026-08-16 09:25
chadmedi 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#asahi-dev · 2026-08-16 09:23
yukaOK nice, T8132 DCS are in the same locations as T6031#asahi-dev · 2026-08-16 09:18
yukaYes, I'm testing on T6000#asahi-dev · 2026-08-16 09:18
jannauT6031_DCS_STRIDE is 0x200000. are you testing on T6000? maybe it's just wrong since it is never used#asahi-dev · 2026-08-16 09:14
yukastride of 0x200000 would make more sense, since all of 0x200000, 0x400000, 0x600000, 0x800000 are readable#asahi-dev · 2026-08-16 09:09
yukano, nevermind, question still stands#asahi-dev · 2026-08-16 09:08
yukabut 0x300000 gives me an SError#asahi-dev · 2026-08-16 09:08
yukaAs I read this, the 4 DCS instances on T6000 should be at 0x200000, 0x300000, 0x400000, 0x500000#asahi-dev · 2026-08-16 09:07
jannauwe probably can switch to parsing segment-ranges#asahi-dev · 2026-08-16 09:07
chaos_princess(trying to throw the dcp driver on the t6031 and see what breaks)#asahi-dev · 2026-08-16 09:06
chaos_princessok, ty. #asahi-dev · 2026-08-16 09:06
yukahttps://github.com/AsahiLinux/m1n1/blob/main/src/mcc.c#L22#asahi-dev · 2026-08-16 09:05
jannauchaos_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#asahi-dev · 2026-08-16 09:05
yukatrying to understand the T6000_DCS_OFFSET and T6000_DCS_STRIDE#asahi-dev · 2026-08-16 08:44
yukaand then it gives the following entries: [(0x101e6e30-0x101e8ec7, enabled), (0x10000000-0x10000000, disabled), (0x101f1a5c-0x101ffc5b, enabled), (0x10000000-0x10000000, disabled)]#asahi-dev · 2026-08-16 08:42
yukafrom top to bottom: start, end, unused/unk, enable#asahi-dev · 2026-08-16 08:42
yukaand this makes sense if the stride is 4, then you read it as columns#asahi-dev · 2026-08-16 08:42
yukaI noticed on t6031, the slot between 2 and 4 has range 0x10000000-0x10000000 and is _disabled_#asahi-dev · 2026-08-16 08:41
yukathis was my previous attempt of staring at it: https://termbin.com/eiitlb#asahi-dev · 2026-08-16 08:40
svennice!#asahi-dev · 2026-08-16 08:37
yukayay, I found a tz_regs mapping for t8140/t6040 which makes sense