#asahi-dev · 2022-03-12 18:26
marcannot locking things properly is not fine#asahi-dev · 2022-03-12 18:26
marcanthat much is fine#asahi-dev · 2022-03-12 18:26
marcanand IIRC it's gated under a .config option#asahi-dev · 2022-03-12 18:26
marcanit's debugfs, it's for debugging#asahi-dev · 2022-03-12 18:19
marcanalso in today's "the kernel is a pile of race conditions and we should all switch to Rust some day", reading /sys/kernel/debug/regmap/*/registers while the regmap is being destroyed crashes the kernel#asahi-dev · 2022-03-12 18:16
marcanpushed, along with the other fixes, to audio/testing#asahi-dev · 2022-03-12 18:15
marcanbecause I can fairly reliably repro the fail by looping unbind -> rebind -> fast speaker-test 4 times, and after making it always do ACTIVE before MUTE, it seems reliable#asahi-dev · 2022-03-12 18:15
marcanany chance that it *always* does 82 -> 80 -> 81 instead of 82 -> 81?#asahi-dev · 2022-03-12 18:15
marcanI have a hunch that that's a workaround#asahi-dev · 2022-03-12 18:15
marcan# [I2CTracer@/arm-io/i2c1] transfer: (start) 70 02 81 (stop) #asahi-dev · 2022-03-12 18:15
marcan# [I2CTracer@/arm-io/i2c1] transfer: (start) 70 02 80 (stop) #asahi-dev · 2022-03-12 18:15
marcan# [I2CTracer@/arm-io/i2c1] transfer: (start) 70 02 82 (stop) #asahi-dev · 2022-03-12 18:15
marcanpovik: from the end of your init log#asahi-dev · 2022-03-12 14:45
marcanpovik: I'm adding debug and yeah, it seems sometimes when it first powers up it goes into overcurrent mode and auto shuts down, but only on that one channel. will keep probing...#asahi-dev · 2022-03-12 14:26
marcanit was more like a buzz#asahi-dev · 2022-03-12 14:24
marcanoh heh, this time I got some weird noise instead of death#asahi-dev · 2022-03-12 14:06
marcanand why#asahi-dev · 2022-03-12 14:06
marcanso the question is when does the error happen#asahi-dev · 2022-03-12 14:06
marcanand the retry timeout is 1.5 seconds which kind of sucks#asahi-dev · 2022-03-12 14:06
marcanlooking at a datasheet for a similar part, these errors are latching#asahi-dev · 2022-03-12 14:05
marcanlol.#asahi-dev · 2022-03-12 14:05
marcan"Certain limitations applied. Contact TI if need to use this bit.#asahi-dev · 2022-03-12 14:05
marcanhonestly this datasheet kind of sucks#asahi-dev · 2022-03-12 14:03
marcanpovik: that bit is the only one that consistently predicts if it's broken or not#asahi-dev · 2022-03-12 13:58
marcan0x49 bit 2 is IR_OC#asahi-dev · 2022-03-12 13:54
marcanpovik: so when lw1 borks, the overcurrent IRQ flag is set and the SAR ADC measurements are invalid#asahi-dev · 2022-03-12 11:43
marcan--depth-1 works though#asahi-dev · 2022-03-12 11:43
marcanright now that history does chain off to the entire kernel, but hopefully Ian will fix that at some point#asahi-dev · 2022-03-12 11:42
marcangit clone --depth=1 https://github.com/AsahiLinux/devicetrees to get a quick clone of the DT stuff, scripts/build.sh to build only the Apple devicetrees#asahi-dev · 2022-03-12 11:25
marcanI guess I'll update manually for now, at least it's all scripted#asahi-dev · 2022-03-12 11:25
marcanso I'll have to set up some local builder or something at some point#asahi-dev · 2022-03-12 11:25
marcanok, I set up the devicetree repo but I don't think updating from a GH action is going to work, you really need the repos to already be fetched to have it finish in a reasonable time#asahi-dev · 2022-03-12 10:37
marcanwe could enable persistent environment, and use that to allow users to override actual boot behavior from the ESP (where "the" has to be the /chosen-specified one)#asahi-dev · 2022-03-12 10:36
marcanyeah#asahi-dev · 2022-03-12 10:33
marcanand then I already had an offset, that's just 0 for AIC2#asahi-dev · 2022-03-12 10:33
marcankettenis: yeah, I just point two iomem pointers at different or same maps, and the error cleanup code unmaps the event one if they aren't equal#asahi-dev · 2022-03-12 10:32
marcanor can get u-boot to read configs from the ESP and then you can override whatever there#asahi-dev · 2022-03-12 10:31
marcanon modern machines you don't normally expect USB to take over boot unless you explicitly set it as such#asahi-dev · 2022-03-12 09:54
marcan:)#asahi-dev · 2022-03-12 09:53
marcancompat hacks like that will start happening after first release if we need them#asahi-dev · 2022-03-12 09:53
marcanit'd be easy to do on linux too but I just want to rip off this bandaid for us :) (since I'm not promising anything yet)#asahi-dev · 2022-03-12 09:53
marcanah, ok, I thought you wanted to keep compat with old drivers#asahi-dev · 2022-03-12 09:53
marcan(if no ESP is specified in /chosen then it should just pick the first though)#asahi-dev · 2022-03-12 09:52
marcanand the explicitly invoked recovery script should be USB -> any ESP in NVMe#asahi-dev · 2022-03-12 09:52
marcanI'd say the default behavior should be specific ESP -> USB (ignore other ESPs in NVMe, always, to avoid confusion)#asahi-dev · 2022-03-12 09:51
marcanyup#asahi-dev · 2022-03-12 09:45
marcanso users can use that as an explicit override#asahi-dev · 2022-03-12 09:45
marcanyeah, that works fine but it'd be nice to have one that explicitly goes for USB first, then NVMe#asahi-dev · 2022-03-12 09:44
marcanso I'm going to try to turn it into a GH action so we have fresh DTs updated when asahi gets pushed#asahi-dev · 2022-03-12 09:44
marcanI'm looking into the DT filtering; seems to work fine, with the state branch a re-filter only takes a minute including all the pulls/merges/mangling involved