#asahi-dev · 2026-09-25 08:35
integralpilotbusy night tonight cause there's 3 patchsets to send out, then on my other laptop im constantly reloading the collegeboard website cause scores are coming out tonight too#asahi-dev · 2026-09-25 08:34
integralpilotim pretty sure it is but i might be misunderstanding#asahi-dev · 2026-09-25 08:34
integralpilotthanks! i guess only one way to find out if its right, will send soon#asahi-dev · 2026-09-25 08:32
svenintegralpilot: no need to cc it, and no idea if that fix is correct. i've seen the lockdep splat before and just ignored it :D#asahi-dev · 2026-09-25 08:26
jannauI got the day wrong but I remembered. unfortunately Miguel was sick so I did not ask him#asahi-dev · 2026-09-25 08:25
integralpilotshould i CC the asahi list for the regmap fix or not really bc its not directly asahi related#asahi-dev · 2026-09-25 08:21
yukayeah probably doesn't work at all, so device tree property it is#asahi-dev · 2026-09-25 08:21
chaos_princesshow would that work with opening /sys/class/gpio or whatever that is called#asahi-dev · 2026-09-25 08:21
yukabut doesn't seem easy to do that#asahi-dev · 2026-09-25 08:20
yukaOr I also considered if it would be possible to get a list of all gpios the which _are actually used_ and then ignoring all others#asahi-dev · 2026-09-25 08:20
chaos_princessi would be against a compatible, gpio numbers sounds like a thing that change based on what device the soc is in, not just the soc itself#asahi-dev · 2026-09-25 08:20
svenit's also describing hardware so should be fine i think#asahi-dev · 2026-09-25 08:20
svensure#asahi-dev · 2026-09-25 08:20
yukaI think device tree property is nicer#asahi-dev · 2026-09-25 08:20
sveneither device tree property or table based on compatible in the driver#asahi-dev · 2026-09-25 08:19
yukaso my solution for that is adding .readable_reg to the regmap_config, but the question is where to source the list of gpios not to read#asahi-dev · 2026-09-25 08:19
yukaOn this device it seems to actually matter#asahi-dev · 2026-09-25 08:18
yukabut we ignored it#asahi-dev · 2026-09-25 08:18
yukayes#asahi-dev · 2026-09-25 08:18
chaos_princessno-restore-gpio-pins exists on previous socs too, no?#asahi-dev · 2026-09-25 08:18
yukawhich happens to be listed in the adt under "no-restore-gpio-pins"#asahi-dev · 2026-09-25 08:18
yuka* of a specific pinctrl_ap gpio#asahi-dev · 2026-09-25 08:18
svenhuh#asahi-dev · 2026-09-25 08:18
yuka(background: on the MacBook Neo you get SErrors trying to read the REG_GPIOx of a specific pinctrl_ap pin#asahi-dev · 2026-09-25 08:17
yukatrying to determine if it really needs a new device tree property but I think yes#asahi-dev · 2026-09-25 08:17
yukaon A18 Pro#asahi-dev · 2026-09-25 08:16
yukaI'm looking into the pinctrl 'protected' pins#asahi-dev · 2026-09-25 08:16
sven"fake m4" :P#asahi-dev · 2026-09-25 08:16
yukanice nice#asahi-dev · 2026-09-25 08:16
svener, yes#asahi-dev · 2026-09-25 08:16
yukasven: you mean A18 Pro?#asahi-dev · 2026-09-25 08:14
chaos_princessoops#asahi-dev · 2026-09-25 08:13
svenchaos_princess: i think he got the day wrong, he wanted to speak to the r4l guys on wednesday. but given that he disappeared then for a few hours i think that's what he did at kernel recipes :D#asahi-dev · 2026-09-25 08:12
svenalright, now that the watchdog thing is applied i can pick up the m4 series this evening#asahi-dev · 2026-09-25 08:12
chaos_princessjannau: as you asked, reminder about the r4l thing#asahi-dev · 2026-09-25 08:11
yukaM5 Pro/Max/Ultra are probably all T6050 but it's a bit unclear at this point#asahi-dev · 2026-09-25 08:10
yukaM5 base is T8142#asahi-dev · 2026-09-25 08:07
myriaWait, all the M5 chips are T6050? Wikipedia lied to me (crazy, right?). Should I change https://github.com/AsahiLinux/docs/pull/278 to reflect this?#asahi-dev · 2026-09-25 06:05
integralpilotfor context, the issue was https://pastebin.com/ZrnMsF0G#asahi-dev · 2026-09-25 05:55
integralpilotas a seperate patch would it be OK to send https://pastebin.com/9b2fKwzV upstream or have i misunderstood smth here#asahi-dev · 2026-09-25 05:55
integralpilotso just removing it fixes all the lockdep warnings#asahi-dev · 2026-09-25 05:55
integralpilotand not during cache reinit either b/c the API asks caller to prevent concurrent access#asahi-dev · 2026-09-25 05:54
integralpilotit looks like the lock actually isnt needed during creation/destruction (where the issue was) cause its not available yet or ppl must have stopped by then#asahi-dev · 2026-09-25 05:53
integralpilotthe gpio driver was giving these lockdep warnings, but its actually the default of regmap, it was allocating memory while holding the GPIO raw spinlock#asahi-dev · 2026-09-25 05:52
integralpilotbtw! when i was running dchid under lockdep to see if there were issues i found smth else in a different part#asahi-dev · 2026-09-25 04:39
integralpilot(to GH)#asahi-dev · 2026-09-25 04:39
integralpilotyuka: https://github.com/IntegralPilot/linux/commits/dchid-v4/ uploaded dchid v4#asahi-dev · 2026-09-24 19:35
yukayeah okay I aligned the model/compatible order to the old version in the patch series I sent out earlier#asahi-dev · 2026-09-24 19:23
jannauthe model/compatible property order and 2 new node order issues but the line length and dcache-size property issues are gone#asahi-dev · 2026-09-24 19:21
jannauyuka: strict dt-style-check from next improves the results for t603*/t8122*