#
…

2021-12-02

01:37chadmed has joined #asahi-dev
02:08yuyichao has quit [Ping timeout: 480 seconds]
02:09chadmed has quit [Quit: Konversation terminated!]
02:40yuyichao has joined #asahi-dev
03:06PhilippvK has joined #asahi-dev
03:06chadmed has joined #asahi-dev
03:09phiologe has quit [Ping timeout: 480 seconds]
03:52kov has quit [Quit: Coyote finally caught me]
03:52kov has joined #asahi-dev
04:03phiologe has joined #asahi-dev
04:07PhilippvK has quit [Ping timeout: 480 seconds]
04:11marcanmaz: ahaha. so I tried setting PORT_LOGIC_SPEED_CHANGE in m1n1 and that didn't work.
04:11marcanthen I added some printfs around it and it worked.
04:11marcan... looks like it wants a ~1ms delay before it. sigh. what's this about...
04:23marcanok, yeah, the write doesn't stick; looks like we need a delay after starting up the port before touching the config regs (which might mean we weren't even applying the tunables properly either...)
04:41marcanyeah, we were missing polling one bit, sigh
05:19chadmed has quit [Remote host closed the connection]
06:24VinDuv has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
06:25VinDuv has joined #asahi-dev
08:14King_InuYasha has quit [Ping timeout: 480 seconds]
08:48mazmarcan: does this require any change in the u-boot/Linux/OpenBSD drivers, or can you keep that in m1n1?
10:25ar has quit [Ping timeout: 480 seconds]
10:39ar has joined #asahi-dev
10:46marcanmaz: this is all in m1n1, already pushed. And since this makes PORT_LOGIC_SPEED_CHANGE unnecessary, if we decide to not care about max speed caps or to put that code in m1n1 too, we can drop the patch I sent entirely
10:55landscape15[m]Has anyone managed to run OpenBSD quite well?
10:57j_eyyes kettenis
10:58landscape15[m]j_ey: thanks! It’s good to know that you don’t need to rewrite all the kernel.
11:07j_eylandscape15[m]: just like linux didnt need a rewrite!
11:12marcansven et al: I think I'm going to rename that t6k bringup branch (which isn't really any more) to something more generic
11:13* svendoesn't use that branch anyway
11:13marcansince that's basically my "stuff sane enough to be on the way upstream to varying degrees" branch
11:13marcanwell, I want people to use it :-)
11:13sveni think jannau has a sane collection of patches like that somewhere as well
11:13kettenisthe current u-boot device trees are based on that branch
11:13landscape15[m]j_ey: So I suppose m1n1 does the hard job. I’m going to test it on my new 13” when I’ll get it.
11:14ketteniswith some extras thrown in for bits where I have (somewhat) sande openbsd drivers ;)
11:14ketteniss/sande/sane/
11:14jnmarcan: is it suitably enough for linux-next to be renamed for-next?
11:14jn(because that's a familiar name)
11:14marcanit's not quite for-next, it's not submission-quality stuff only
11:14marcanit's more like devel
11:15jni see
11:15marcanI rebase it frequently as things get merged
11:16marcanfor-next doesn't really make sense for us because we don't have a subsystem tree; instead I have things under asahi-soc/ that I send arnd_, but that's mostly DT/misc fixes, not drivers
11:16marcanI wonder if there's some kind of name between "for-next" and "devel" that's appropriate...
11:17kettenis"integration"
11:18svenwe'll have a (boring) subsystem tree for rtkit and sart eventually i guess
11:18marcannot sure what the upstreaming path for those is actually
11:18svensart probably together with nvme because it's really only used there
11:19svendunno about the rtkit stuff
11:19svenit unfortunately doesn't really fit into the remoteproc system
11:21marcankettenis: I like the meaning but dang that's long :-)
11:28marcaneh, what if I just call it 'asahi'
11:28kettenisworks for me ;)
11:28marcanit's probably going to evolve into the kernel branch we ship to people sooner or later anyway (in bleeding edge packages)
11:32landscape15[m]marcan: what is “asahi” branch for?
11:33marcanthings I actually want people to test :p
11:34marcani.e. code that is either on the way upstream or being developed with that goal, that is good enough for people to test and use
11:34marcanbasically an integration of everything people are working on
11:35as400 has joined #asahi-dev
11:35_jannau_https://github.com/jannau/linux/tree/apple-m1-exp_v5.16-rc3_1 is t600/bringup with fixes, dts additions and patches sent to kernel mailing lists rebased onto the latest rc
11:37marcanasahi/linux.git/asahi is already rebased on latest rc :)
11:37landscape15[m]marcan: Ok, so it’s quite close to a well-rounded pre-release
11:38marcanyes, it should eventually become something we can ship to users, once a few loose ends are tied up
11:39marcan_jannau_: mostly just those SART fixes at the end, right? I imagine sven will want to pull those into his branch
11:40_jannau_marcan: you've dropped the t600 PMGR devicetree nodes in the latest t6000/bringup-work rebase ans asahi
11:40marcanhuh, where did that go
11:43marcanah yeah, that got dropped a while ago actually
11:43_jannau_I guess you replaced all pmgr commits with tree you send out which can't include t600 changes
11:46marcanah, forgot about that one, thanks for the reminder
11:46marcanmind if I just manually munge that in?
11:47_jannau_merge and squash as you like
11:50svenI think I already squashed the sart fixes in the rtkit branch
11:50svendunno if I pushed though
12:02svenhm, guess I should also add power-domains to that binding
12:05marcanplease do :)
12:36marcan_jannau_: I think I got everything into asahi, want to take a look
12:45jannaumarcan: looks good. thanks
12:47jannauis it to early to make asahi the default branch for AsahiLinux/linux?
12:49marcanjannau: I just did :)
12:49marcanhad the same idea :p
13:20yuyichao has quit [Ping timeout: 480 seconds]
13:44yuyichao has joined #asahi-dev
13:44Gaspare has joined #asahi-dev
14:03robher_ has quit []
14:03robher has joined #asahi-dev
14:08marcanarnd_: I'm a bit confused about what path the PMGR driver should take upstream. It's under drivers/soc, which doesn't have anyone in charge of it at the top level AIUI. Linus Walleij acked it.
14:08arnd_marcan: send it to soc@kernel.org, but separately from the DT changes
14:10marcanack, do you want all the related DT changes (bindings changes to add power-domains props, instantiating PMGR & adding domains) together in a DT pull along with other DT changes, and just the driver separately?
14:11marcan(I'm guessing the bindings for PMGR itself would go with the driver)
14:11the_lanetly_052 has joined #asahi-dev
14:11marcan(in that case, there's a dependency, so I guess I should stack the branches in the right order as usual?)
14:12aleasto has joined #asahi-dev
14:13marcanalso nobody reviewed the actual DT change yet (in particular v3 adds *all* the domains...)
14:14marcansven or jannau: mind giving a look over?
14:14svenuh, sure. got a link to the thread?
14:14marcanyeah, sec
14:14marcanI should've CCed you... :/
14:14svenhrm, don't think i got anything
14:15marcanyeah, I didn't
14:15marcanI'm saying I should've
14:15svenah, heh
14:15sveni'll grab it from the list and take a look this evening
14:15marcancool, thanks!
14:16marcanarnd_: ^^
14:44arnd_marcan: yes, all the DT changes should come together, separately from the driver changes
14:45arnd_the idea is that each half should be regression-free and tested without the other half, to ensure that there are no incompatible binding changes
14:45arnd_obviously any added features may only become available once both branches are merged
14:54kettenismarcan, sven: dr_mode changed from "host" to "otg" on the asahi branch and that makes u-boot unhappy
14:57the_lanetly_052 has quit [Ping timeout: 480 seconds]
15:06marcanarnd_: I'm mostly wondering about the DT checker; if that is to pass then all the bindings changes should come along with the DT changes, and the driver would be completely separated from its related binding changes. is that what you expect?
15:06marcankettenis: *points at _jannau_*
15:07sventhe default dr_mode should be otg anyway
15:07svenwe can just drop that from the DT but that also sounds like a bug in u-boot
15:07arnd_marcan: that is usually the easiest way, the alternatives are to have the dt binding patch first, using the same commit for both branches, or to do it over more than one merge window
15:08arnd_some subsystem maintainers prefer the binding changes to go in with the driver, obviously I don't care if I merge both branches anyway
15:09marcancool, I'll split it out like that and send it tomorrow then :)
15:09kettenissven: having those ports default to otg instead of host doesn't make sense to me on these machines
15:11sveni'll have to check those node again anyway, but iirc there was another property for the default mode
15:12kettenisrole-switch-default-mode = "host";
15:13kettenisbut u-boot defenitely doesn't look at that
15:13svenas i said, i think the default mode for dr_mode is otg anyway so we can just drop that from the DT if that helps
15:14sveni think i just put something in those node that made it work for now. i'll have to re-check them once the drd3 maintainer comments on that dumb reset quirk anyway
15:14Gaspare has quit [Quit: Gaspare]
15:15kettenisthat seems to work
15:26kettenisthose dwc3 nodes have not yet been sumitted upstream isn't it?
15:27svenwe kinda need to know how this dumb reset quirks looks like in the end. though i guess i could submit the binding + DT changes separately from that
15:27kettenisI think so; the ports are usable as-is
15:32kettenisanyway, it would be great you and/or jannau could remove that dr_mode property such that we don't run into this issue again later
15:35kettenisI suppose I'd need to implement support for the hpm chip in u-boot to get role switching to work properly?
15:36svenonly if you want to react to role switch notifications from that chip
15:37svenin linux you can also write to some sysfs node to trigger a role switch and that works even without support for that hpm chip
15:37sven(as long as m1n1 initialized it with that SSPS command)
15:41kettenisah, so adding support for the role-switch-default-mode property is what I need then
15:58aleasto has quit [Quit: Konversation terminated!]
16:02aleasto has joined #asahi-dev
16:08as400 has left #asahi-dev [#asahi-dev]
16:16___nick___ has joined #asahi-dev
16:17___nick___ has quit []
16:18___nick___ has joined #asahi-dev
16:31povikthis won't work with interrupt-parent=<&pinctrl>, or will it?
16:34kettenispovik: I think it should
16:34povikhm, seems it will, if i2c bus code fills i2c_client->irq according to DT
16:35kettenisI'd use interrupts-extended in this context though
16:35povikwhat does that do?
16:35kettenisit combines the parent and the actual (gpio) interrupt specification
16:36povikah, TIL
16:39kettenisthat is the keyboard interrupt
17:20Gaspare has joined #asahi-dev
17:21Gaspare has quit []
17:21svenOh fun, 1160 lines of pmgr nodes :D
17:23Gaspare has joined #asahi-dev
17:31crabbedhaloablut has joined #asahi-dev
17:31loki_val has quit [Ping timeout: 480 seconds]
17:40crabbedhaloablut has quit [Ping timeout: 480 seconds]
17:40crabbedhaloablut has joined #asahi-dev
18:11gig has quit [Remote host closed the connection]
19:00Mary has quit [Quit: The Lounge - https://thelounge.chat]
19:01Mary has joined #asahi-dev
19:03Mary has quit []
19:06Mary has joined #asahi-dev
19:13yuyichao has quit [Quit: Konversation terminated!]
19:14___nick___ has quit [Ping timeout: 480 seconds]
19:34Gaspare has quit [Quit: Gaspare]
19:48yuyichao has joined #asahi-dev
20:11Gaspare has joined #asahi-dev
20:12aleasto has quit [Remote host closed the connection]
21:07Gaspare has quit [Quit: Gaspare]
21:23Gaspare has joined #asahi-dev
21:25fgfhmnrtry4r4t[m] is now known as iPhowned[m]
22:24Gaspare has quit [Quit: Gaspare]
23:49kode54 has quit [Quit: The Lounge - https://thelounge.chat]
23:49KDDLB has quit [Quit: The Lounge - https://thelounge.chat]
23:51KDDLB has joined #asahi-dev
23:51kode54 has joined #asahi-dev
…