#
#asahi-dev · 2025-03-18 13:34
fl0_idthis is based on this: https://github.com/AsahiLinux/m1n1/pull/426 so yes it would have to be dealt with. But t6031 was also merged before doing that, so I think there's no reason not to add t6030
#asahi-dev · 2025-03-18 13:34
nickchanBut I guess there is no need to deal with that yet when hv is broken for plenty other reasons
#asahi-dev · 2025-03-18 13:33
nickchanid imagine hv with different timer frequencies between EL would be really bad
#asahi-dev · 2025-03-18 13:31
nickchanfl0_id: do you not need to deal with timer registers? the 1ghz clock stuff
#asahi-dev · 2025-03-18 13:30
fl0_idthough force pushing is a good idea in this case, didn't even think of that
#asahi-dev · 2025-03-18 13:29
fl0_idnickchan ok true. Though I still think I'm first waiting for some feedback
#asahi-dev · 2025-03-18 13:29
nickchanfl0_id: edit some timestamp or something and then force push will make it rerun
#asahi-dev · 2025-03-18 11:02
fl0_id https://github.com/AsahiLinux/m1n1/pull/418/files#diff-b5fdbbf0714bc26b69cb2a8418c84f4ffd187f5cfb05faca3d79730e483e2dd7
#asahi-dev · 2025-03-18 11:02
fl0_idother question - this file is from a not accepted PR due to binary RE-ing of the author (on other drivers) - but as it seems to just rename mcc things to make t6031 things also apply to t6030 things, would it be acceptable to work off of it to enable mcc for t6030?
#asahi-dev · 2025-03-18 10:43
fl0_idI would just rerun it, but for obvious reasons I cannot do that
#asahi-dev · 2025-03-18 10:43
fl0_iddo you by any chance know about this rust fmt error in my PR? seems more like a CI fluke as I didn't touch any rust code.
#asahi-dev · 2025-03-18 10:42
fl0_idnickchan good to know
#asahi-dev · 2025-03-18 00:24
nickchanI mean, other than that offset obviously
#asahi-dev · 2025-03-18 00:24
nickchanfl0_id: the cpu start interface has remained compatible for like some 10 (?) years
#asahi-dev · 2025-03-17 19:34
alyssayippee!
#asahi-dev · 2025-03-17 19:34
mazI'm going to turn a blind eye on them for now, as things seem to be working OK on both t8103 and t6020 with my current set of changes.
#asahi-dev · 2025-03-17 19:32
mazthey are indeed totally separate. and poking at them instead of PORT_LTSSMCTL doesn't seem to result in anything remotely useful.
#asahi-dev · 2025-03-17 19:25
jannauerr, I can't read or add. those don't overlap with PORT_LTSSMCTL
#asahi-dev · 2025-03-17 19:01
mazjannau: I guess there is nothing really needed from a functional pov there, so I'll keep ignoring it for now.
#asahi-dev · 2025-03-17 18:59
jannaumaz: my best guess (maybe recollection) is caution due to the phy change. the ADT has reg entries with the per port LTSSM addresses
#asahi-dev · 2025-03-17 18:08
mazdo you happen to know what this is about?
#asahi-dev · 2025-03-17 18:08
mazhowever, the driver always pokes at a fix offset in the port range.
#asahi-dev · 2025-03-17 18:07
mazjannau: I'm looking at respinning the t602x PCIe patches again, and noticed that the DT describes per-port LTSSM ranges.
#asahi-dev · 2025-03-17 14:34
fl0_idI kind of think this rustfmt error is just a CI fluke or because the image used changed or sth
#asahi-dev · 2025-03-17 13:56
fl0_idonly somehow rust fmt check seems broken in CI
#asahi-dev · 2025-03-17 13:55
fl0_idapart from that I made the t6030 bringup commits a bit prettier and merged them with t6031 (like f.e. have t6030 in order before t6031) https://github.com/AsahiLinux/m1n1/pull/450
#asahi-dev · 2025-03-17 13:52
fl0_idci cargo fmt fails with "error: no such command: `fmt`" is that normal? I didn't change anythin there
#asahi-dev · 2025-03-17 04:22
nickchanbut then again, that machine barely has any reason to exist
#asahi-dev · 2025-03-17 04:22
nickchanis the j180d pcie slots like not functional without smc
#asahi-dev · 2025-03-16 19:30
mischa85upon closer inspection, those are also present in t6031 adt. misc-acg-offset = 0x98000, misc-cores-offset = 0x88000 are the same on m4/m3 but cluster-ctl-offset is 0x18000 on t6031 and 0x20000 on t6041
#asahi-dev · 2025-03-16 17:22
mischa85thanks jannau
#asahi-dev · 2025-03-16 17:22
mischa85i'm so glad i have a working shell for all this stuff
#asahi-dev · 2025-03-16 17:21
mischa85so instead of feeding offset 0x20000 to smp_start_cpu i think i should be doing something else to that register
#asahi-dev · 2025-03-16 17:19
fl0_idm4 chip designer be like "i have this fancy new way to do this, finally have time to do it for m4"
#asahi-dev · 2025-03-16 17:19
mischa85the good news i mapped the whole register range by bruteforcing
#asahi-dev · 2025-03-16 17:18
mischa85maybe this will be a hint to how pmgr is done on m4
#asahi-dev · 2025-03-16 17:18
mischa85nope it just goes straight into firing the cores
#asahi-dev · 2025-03-16 17:17
fl0_idmischa85 yeah just wanted to say 0x88000 is same as m3. does m3 do any tickling?
#asahi-dev · 2025-03-16 17:16
mischa85so my guess is that offset 0x20000 needs to be tickled in some way en then the cores are to be enabled from 0x88000 offset, same as m3
#asahi-dev · 2025-03-16 17:15
mischa85or maybe i should be using my brain for a moment. the t6041 devicetree is full of mysteries but there are some new pairs in pmgr: misc-acg-offset = 0x98000, misc-cores-offset = 0x88000, cluster-ctl-offset = 0x20000
#asahi-dev · 2025-03-16 16:10
mischa85okay i've exousted all the possibilities, cannot start the cpu. i have a list of addresses that result SError or Failed. only thing i could figure out is that offset 0x20000 fails, but the next call makes the system crash, fans go on (maybe safety mode?)
#asahi-dev · 2025-03-16 15:58
svenalso much less awkward if all the probing and resource allocation, etc. happens directly inside mfd
#asahi-dev · 2025-03-16 15:58
svenokay, this is looking much more manageable without the backend_ops indirection
#asahi-dev · 2025-03-16 14:50
chaos_princessok i see now
#asahi-dev · 2025-03-16 14:45
jannauchaos_princess: I can't follow. spi-hid and mtp are fully independent HID transport drivers
#asahi-dev · 2025-03-16 14:43
chaos_princessWhat do you mean by that, don't we need it for mtp? Or am i thinking about the wrong thing?
#asahi-dev · 2025-03-16 14:38
jannausven: no objection from stripping the backend modularity out. I plan to do the same for spi-hid
#asahi-dev · 2025-03-16 14:38
jannauwe could also turn wifi/bluetooth on in m1n1. it has smc gpio because it's needed for display
#asahi-dev · 2025-03-16 14:34
jannaumaz: ethernet should work without smc
#asahi-dev · 2025-03-16 13:48
svenyet another reason to get this upstream

plus ›