#
…

2022-09-22

00:01thelounge7571340 has joined #asahi-dev
00:10SSJ_GZ has quit [Read error: Connection reset by peer]
00:10SSJ_GZ has joined #asahi-dev
00:28SSJ_GZ has quit [Ping timeout: 480 seconds]
01:00DragoonAethis has quit [Quit: hej-hej!]
01:00DragoonAethis has joined #asahi-dev
01:00thelounge7571340 has quit [Read error: Connection reset by peer]
01:03thelounge7571340 has joined #asahi-dev
01:49thelounge7571340 has quit [Remote host closed the connection]
01:51thelounge7571340 has joined #asahi-dev
02:30dmmcf has joined #asahi-dev
02:51thelounge7571340 has quit [Read error: Connection reset by peer]
02:55thelounge7571340 has joined #asahi-dev
03:10chadmed has quit [Remote host closed the connection]
03:16dmmcf has quit [Quit: dmmcf]
03:35kov has quit [Quit: Coyote finally caught me]
03:55thelounge7571340 has quit [Remote host closed the connection]
03:57thelounge7571340 has joined #asahi-dev
04:57thelounge7571340 has quit [Remote host closed the connection]
05:00thelounge7571340 has joined #asahi-dev
05:07SSJ_GZ has joined #asahi-dev
05:57jannaumarcan: I've still haven't heard anything from Joerg. he handled some iommu fixes yesterday. I would take the dart t6k dt binding commit and reply to it that you will merge since you have dt changes which depend on it for verification (if you want to prepare/send) your pull request today
06:00thelounge7571340 has quit [Read error: Connection reset by peer]
06:02thelounge7571340 has joined #asahi-dev
06:03jannauprobably easier as well as it then only depends on a single other tree (sound/for-6.1, https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git/log/?h=for-6.1)
06:56MajorBiscuit has joined #asahi-dev
07:01Major_Biscuit has joined #asahi-dev
07:02thelounge7571340 has quit [Read error: Connection reset by peer]
07:05thelounge7571340 has joined #asahi-dev
07:08MajorBiscuit has quit [Ping timeout: 480 seconds]
08:05thelounge7571340 has quit [Remote host closed the connection]
08:08thelounge7571340 has joined #asahi-dev
09:08thelounge7571340 has quit [Remote host closed the connection]
09:10thelounge7571340 has joined #asahi-dev
09:42akemin_dayo has quit [Ping timeout: 480 seconds]
09:52thelounge7571340 has quit [Ping timeout: 480 seconds]
09:53akemin_dayo has joined #asahi-dev
10:54thelounge7571340 has joined #asahi-dev
11:06kov has joined #asahi-dev
11:53thelounge7571340 has quit [Remote host closed the connection]
11:58thelounge7571340 has joined #asahi-dev
12:11marcanok, applied the binding and t6k series to asahi-soc/dt. Let me do some smoke tests on it and I'll send it to arnd.
12:12marcansven: wouldn't be surprising if I got some EPIC functions wrong
12:20svenyeah, fixing those made HPD work
12:34marcanah, hm, we have dependencies on MCA bindings that were merged via another tree :/
12:39marcanarnd: There are 3 patches in that tree starting from v6.0-rc1, two of them are code, one is the binding (all for the same thing). I can base the DT series on that point and send you a pull for that and you can merge it in, or I can just do the DT series and then the checker will complain until both branches are merged...
12:40tdamdspurlt^ has joined #asahi-dev
12:43marcanand ha, the binding for apple,aic.yaml is wrong and says fiq-index instead of apple,fiq-index is wrong. that needs to be fixed, but it looks like that has been there forever? I guess the dt checker started catching that recently?
12:44_jannau_marcan: that's fixed and in 6.0-rc6
12:44marcanah, good, couldn't find the patch
12:45arndmarcan: I'm confused now, which binding patch is this? I don't want to merge large chunks of the asoc tree, so rebasing on top of that would not work unless the patches are right on top of rc1
12:46marcanthe 3 patches are in fact right on top of rc1
12:46arndis the binding the first one?
12:46marcanit's just the binding patch went in last, so the 2 code patches are in that tree
12:49marcanah but hold on, looks like for-6.1 was rebased? I got those commits from the hashes as they were applied to for-next, but that might not work now...
12:50marcanlet me check if they're proper parents of for-6.1
12:50marcanah, they are
12:51marcanso what I said still stands: I can rebase on that point and that history is in what's going into for-6.1, so it'll merge cleanly
12:51marcanbut it does mean pulling in the 2 code patches since they came first
12:52marcan6ed462d1c11675064 in the above tree fwiw
12:52marcanotherwise, we can punt the MCA part of the DTs to next cycle
12:57thelounge7571340 has quit [Remote host closed the connection]
12:59thelounge7571340 has joined #asahi-dev
13:00marcanarnd: let me know what works best for you
13:06arndmarcan: I'll take the branch without the binding patch then. The warning does not show up in a plain allmodconfig build, and the driver change is a bit larger than what I'm comfortable with having in the dt branch
13:08arndI sometimes merge in smaller dependencies outside of arch/*/boots/dts/* when there is a strong reason, but otherwise try to keep the arm/dt branch having only dt changes to ensure that there are no incompatible binding changes
13:09marcangot it, I'll just send you the DT series then. There is also that FIQ fix that is in -rc6, but that was a longstanding problem anyway, not a regression.
13:11arndideally you should try to do the binding changes before code changes in another branch, so you can just merge in the binding commits (on top of rc1) into the dts branch
13:12povikmarcan: don't forget the ADMAC reset series then
13:12povikah, that's on me maybe? how did i order them?
13:18povikbroonie reordered them, because i threw one patch into the series that wasn't for him
13:29marcanpovik: I'll take the reset DT/binding patches via our tree if that works for you?
13:31povikyes, thar's what i suggest in the cover letter :)
13:35marcanI rebased your audio stuff onto broonie's tree (or some point on it); it was mostly trivial conflicts, so no issue there
13:36marcandoing an asahi-wip rebase on top of v6.0-rc6 + that + asahi-soc/dt
13:37tdamdspurlt^ has quit [Remote host closed the connection]
13:39_jannau_marcan: in the previous asahi-wip t6002-j375d.dts somehow ended up with a stray 'bluetooth0 = &bluetooth0;'
13:42marcanlooks like a bad merge, weird. I'll fix it.
13:48_jannau_yes, I suspect I missed for the bluetooth dts commit to check kdiff3's automatic conflict resolution after I created t600x-j375.dtsi
13:49jluthra has quit [Remote host closed the connection]
13:49povikmarcan: heads up on smoke testing: you will probably hit a WARN_ON in the reset subsystem
13:50povik(fixed in https://tpaste.us/oOwB which i should submit)
13:50povikthe WARN_ON should be benign though
13:51jluthra has joined #asahi-dev
13:53marcanI didn't see that, but I think I don't have the reset patches in bits/? (only the binding/dt changes)
13:54marcanI do see a bunch of this though:
13:54marcan[ 12.105159] apple-mca 39b600000.mca: ASoC: error at snd_soc_dai_hw_params on mca-pcm-1: -22
13:54marcan[ 12.106198] Secondary: ASoC: error at __soc_pcm_hw_params on Secondary: -22
13:54marcan[ 12.107021] Secondary: ASoC: error at dpcm_fe_dai_hw_params on Secondary: -22
13:57_jannau_ think those are expected with disabled speakers
13:57povikyes, if you are opening a subdevice with no route, essentially
13:58marcanpovik: I assume your reset series supersedes dmaengine: apple-admac: Pull shared reset control?
13:58povikit does
13:58thelounge7571340 has quit [Remote host closed the connection]
14:00povikthat was before i realized i can do pulses on shared resets still
14:00povikbefore i thought the reset subsystem can only do asserts/deasserts on shared resets
14:00marcanok, added that and fixed the resulting conflict, merging again
14:01thelounge7571340 has joined #asahi-dev
14:10marcansmoke test looks good; pushed everything to asahi-wip.
14:11marcanarnd: how much in a rush are you? I can send the pull now, or push a kernel out to -dev and let folks test it a couple days first to make sure the series as merged is good
14:12arndmarcan: I still have a bit of a backlog to handle first, no need to send it right away
14:12marcanack, expect it this weekend then
14:12marcanthanks for the help :)
14:13arndmarcan: is it in linux-next already?
14:13marcanI don't think linux-next pulls us?
14:15marcanI don't actually know how we get into linux-next :)
14:15arndah, I see. You may want to email Stephen Rothwell <sfr@canb.auug.org.au> cc lkml then to give a URL to add to linux-next.
14:16arndmost platform maintainers have their tree added to linux-next, which gives a little wider CI testing from all the bots before I pull the contents
14:16marcanyeah, that makes sense
14:17marcanI guess I should keep a for-next branch I merge trees with patches into then
14:18arndyes, that also documents nicely what you plan to send me, which can come in handy when I look at the contents early, or for other folks that are interested
14:18marcancool, makes sense!
14:19arndmost trees have some variant of "for-next" and an an additional "fixes" branch, with the latter being for stuff that should get in before the merge window but could also benefit from linux-next testing
14:21marcanah, right, I'll make a (trivial) fixes branch too and mention it then
14:22marcan(well, I already had one, I'll just fast forward it so it's more obvious it's all merged already)
14:25Major_Biscuit has quit []
14:25MajorBiscuit has joined #asahi-dev
14:29marcanemail sent :)
14:32marcanasahi-6.0-rc6-1 tagged and pushed, that's my prior smoketest plus the reset fix change (assuming it works, about to find out with a proper kernel package now)
14:42yrlf has quit [Quit: The Lounge - https://thelounge.chat]
14:43yrlf has joined #asahi-dev
14:47yrlf has quit []
14:48yrlf has joined #asahi-dev
14:57marcanpackage pushed, smoke tested on t6000, seems to work
14:57marcanhave at it :)
15:01thelounge7571340 has quit [Remote host closed the connection]
15:04thelounge7571340 has joined #asahi-dev
15:16yrlf has quit [Quit: The Lounge - https://thelounge.chat]
15:16yrlf has joined #asahi-dev
15:19yrlf has quit []
15:20yrlf has joined #asahi-dev
15:37zzywysm_marcan: why does asahi-wip have hundreds of seemingly non-asahi-related, vaguely sound-ish commits on top of it?
15:38j`eybits/070-audio
15:39_jannau_1it contains sound/for-6.1 for mca dt-binding dependency
15:39zzywysm_ah, thanks
15:40_jannau_also replaces the audio bits with the ones already queued for 6.1
16:00svenhuh, does dcp.py crash DCP for anyone?
16:02_jannau_before displaying anything?
16:03_jannau_it has no teardown code
16:03thelounge7571340 has quit [Remote host closed the connection]
16:04_jannau_on dcp or dcpext0?
16:04_jannau_mac mini?
16:04svendcp0 on mac mini
16:05_jannau_it didn't when I created the pull request
16:05svenwait.. it worked now I think
16:05svenand it also complains about "[syslog] * [PmgrService.cpp:319][AFK]_pmgrConfigVideoClock Failed to configure video clock freq= 74250000" it seems
16:06svenokay.. it sometimes crashes for some reason :/
16:08thelounge7571340 has joined #asahi-dev
16:09svenlooks like it reliably crashes when I have the cable already connected during boot
16:11svenlooks like "[syslog] * [nifiedPipeline.cpp:6553]set_digital_out_mode returned 80000104" is the actual error
16:11sven(for dcpext)
16:11jannauworks for me with chainloaded m1n1 but not with the not that old installed m1n1
16:12jannauI guess it crashes because we continue after the set_digital_out_mode() error
16:12svenregular dcp.py crashes
16:12svenusing regular dcp
16:12sveneven when chainloading m1n1 before
16:13svenbut maybe my installed m1n1 is much too old
16:13jannauah, I overread the dcpext
16:14svenboth dcp (sucessful) and dcpext (fails set_digital_out_mode) complain about "[syslog] * [PmgrService.cpp:319][AFK]_pmgrConfigVideoClock Failed to configure video clock freq= 74250000"
16:14svenso that video clock thing is probably a red herring
16:14jannaudoes the installed m1n1 already shuts dcp down after configuring the display?
16:15svenI think so. it prints "TTY> display: Sleeping DCP (external)"
16:15svenand "TTY> pmgr: resetting device 0.DISP0_CPU0"
16:18jannauno "Failed to configure video clock freq=" here for dcp
16:19svenmaybe it's something in this strange dp -> hdmi -> usb3 chain
16:19svenoh, i dunno if you need to enable extra debug for that message
16:19svenstart ep 0x20 and then
16:19sven dcp.system.wait_for("system")
16:19sven dcp.system.system.setProperty("gAFKConfigLogMask", 0xffff)
16:33jluthra has quit [Remote host closed the connection]
16:33svenmarcan: how bad is the DCP firmware? I’m tempted to just reverse and figure out what that error means
16:34jluthra has joined #asahi-dev
16:35jannaudoes that depend on your EPIC fixes? I'm getting an error after a few system messages in "EPICCmd.parse_stream(fd)"
16:36jannauor does it depend on statrting the other endpoints as well?
16:37svenhuh, I don’t think so
16:38sventhe epic fixes were just required to get hpd to work
16:38svenand it was mostly a different group/cmd and different way to specify arguments
16:38svennormal DCP.py shouldn’t even use those calls
16:44jannauany fixes on dcp tracer side?
16:44svenno, just prettier epic tracing
16:45MajorBiscuit has quit [Quit: WeeChat 3.5]
16:45jannauworks without hv
16:52jannaustill no "Failed to configure video clock freq=" messages
16:52svenstrange
17:00jannauyou still get more syslog messages
17:01svendcp.start()
17:01svendcp.start_ep(0x37)
17:01svendcp.start_ep(0x20)
17:01svendcp.system.wait_for("system")
17:01svendcp.dcpep.initialize()
17:01svendcp.system.system.setProperty("gAFKConfigLogMask", 0xffff)
17:01sventhat's all i have in dcp.py
17:01jannauI have that before starting dcpep
17:02svenjust dcp instead of dcpext
17:07jannauand dcp instead of dcp_iboot and adding those endpoints to DCPClient
17:07thelounge7571340 has quit [Remote host closed the connection]
17:07jannauis what I have
17:08sventhat’s what I have as well
17:10thelounge7571340 has joined #asahi-dev
17:15jannauI don't see "[system] Ignoring report on channel 3" in your output
17:17svenuhhh… I don’t even know what that is :/
17:20jannauextended log works with dcpext_iboot.py
17:45jannauis your display on and displaying something when you run dcp.py?
17:45jannau"sr_setProperty(IOMF/M3TimingParameters = {'subframe-duration-nclks': 0 ..." suggests it's not
17:48alyssasven: IIRC thee are some failures in the dcp syslog with macOS, lol
17:49alyssaI don't remember if this is one of them but it may well be
17:49svenjannau: i saw some rainbow like color thingy
17:49alyssadcp being broken is the status quo
17:49alyssaeh. it just means you need to lower your expectations somewhat :-p
17:50svenI don’t mind if DCP complains as long as it shows something on this usb-c port
17:50svenit’s so damn close :(
17:52svenuh.. I think I do?
17:52jannauI don't know why I thought it was already merged
17:52jannauok, I'm not
17:52svenI merged it into my branch
17:54alyssawhy don't any key bindings work for me in firefox now ..
17:56alyssaworks after a restart, oh well
17:57jannauextended logging works now and I get "_pmgrConfigVideoClock Failed to configure video clock freq= 74250000" but it still works, even for an uninitilized display
18:00svenok, so that thing is a red herring then
18:01svenSo all we have is a weird error code :(
18:04jannaudcp still doesn't work for you? did you revert the changes to rt_bandwidth_setup_ap for dcp\
18:06skrzyp has quit [Quit: -help]
18:06svenit works if I don’t have anything plugged in during boot
18:07alyssadcp0 doesn't work?
18:07jannauthat could be a hint that your installed m1n1 is too old
18:07svenyeah, could be. I also don’t care too much
18:07alyssam1n1 has a half-life of a few momnths, you know
18:08svenjust wanted to compare DCP vs dcpext
18:08alyssasven: also, what OS/firmware version are you on?
18:08svenwho knows
18:08svenI think I updated at the last major release
18:08alyssathat matters a lot, dcp versioning is very picky.
18:09alyssaI think 12.3 is what we support these days for dcp
18:09svenyeah, I think I have that
18:10thelounge7571340 has quit [Remote host closed the connection]
18:12jannau12.3 is "system-firmware-version = iBoot-7459.101.2"
18:13svenwill check tomorrow, DCP annoyed me enough for today ;)
18:14thelounge7571340 has joined #asahi-dev
18:15gladiac has quit [Quit: k thx bye]
18:53thelounge7571340 has quit [Ping timeout: 480 seconds]
19:00CME has quit [Ping timeout: 480 seconds]
19:24Glanzmann has joined #asahi-dev
19:26Glanzmannmarcan: If we're supposed to test the rebase, than my rcu hangs are gone, but I have no sound on the mini with the new kernel: dmesg: https://pbot.rmdir.de/BwoepFUZlYzjxF-0dLOStg if not disregard.
19:31Glanzmann has quit [Quit: EOF]
19:35marcansven: the problem with those error codes is a lot of them are highly overloaded, so it may or may not help find the place in the firmware, but you can certainly try
19:35marcanthe firmware is, uh, variable
19:36marcanC++ so lots of vtables I'm too lazy to trace
19:36marcanbut you can usually find thingsd
19:36marcanI did work out that dcp.system.system.setProperty thing from firmware only
19:39svenhighly overloaded doesn’t sound like fun :/
19:44povikGlanzmann: you should enable cs42l83
19:44povikstill a weird error you get
19:44povik[ 2.346125] cs42l42 2-0048: ASoC: error at snd_soc_component_update_bits on cs42l42.2-0048 for register: [0x00001208] -6
19:54thelounge7571340 has joined #asahi-dev
19:55Glanzmann has joined #asahi-dev
19:56Glanzmannpovik: Thanks, building.
20:02povikunderstand the error now -- there's a race that can make the codec attach to a sound card before it passes the device id check
20:03povikthen when it fails the check, the device is reset, but there's a window when the sound card can ask for settings on the codec after that
20:03povikanyway we should remove the cs42l42 compatible on the headphone codecs, adding to TODOs
20:15Glanzmannpovik: I see. Cool. Have a good night sleep.
20:18povikyou too!
20:21Glanzmann has quit [Quit: Thanks, n8]
20:33dingodoppelt has quit [Quit: ZNC 1.9.x-git-170-9be0cae1 - https://znc.in]
20:35dingodoppelt has joined #asahi-dev
20:36chengsun_ has quit [Quit: Quit]
20:37chengsun has joined #asahi-dev
20:42alyssa has quit [Quit: leaving]
20:54thelounge7571340 has quit [Remote host closed the connection]
20:57thelounge7571340 has joined #asahi-dev
21:02CME has joined #asahi-dev
21:10SSJ_GZ has quit [Ping timeout: 480 seconds]
21:12thelounge7571340 has quit [Ping timeout: 480 seconds]
21:28jannaunice, module and firmware loading working in the initramfs with tools/run_guest_kernel.sh via multiple (3) cpio archives
21:33thelounge7571340 has joined #asahi-dev
21:58systwi has joined #asahi-dev
22:17chengsun_ has joined #asahi-dev
22:20chengsun has quit [Ping timeout: 480 seconds]
22:33thelounge7571340 has quit [Remote host closed the connection]
22:36thelounge7571340 has joined #asahi-dev
23:35thelounge7571340 has quit [Remote host closed the connection]
23:39thelounge7571340 has joined #asahi-dev
…