#asahi · 2021-09-15 14:38
svenand if you take a look at all those tipd commits you'll notice that they are small diffs#asahi · 2021-09-15 14:37
svenand it'll be two series. one for i2c and another one for tipd#asahi · 2021-09-15 14:37
sventhree commits of that branch are already almost upstream#asahi · 2021-09-15 14:36
sven(possibly "system power state switch")#asahi · 2021-09-15 14:36
sventhat's not new fwiw. it's just that SPSS command for the TI chip#asahi · 2021-09-15 14:30
svenhttps://github.com/AsahiLinux/linux/commits/sven/i2c-tipd-WIP this does usb hotplug in a very wrong and hacked way but it allows testing i2c (still WIP) and the tipd patches (mostly happy with those)#asahi · 2021-09-15 11:17
svenyup#asahi · 2021-09-15 11:14
svengiven that i usually only finish the slides (or the demo) maybe a few hours before the presentation i'm kinda sure i'd never be able to record one in time#asahi · 2021-09-14 12:43
svenbut that was my plan if that doesn't work#asahi · 2021-09-14 12:43
svenno, i just figured i'd try and see if someone here happens to be able to test this first#asahi · 2021-09-14 12:38
sveni guess this TPS6598x chip might also be used some intel hardware#asahi · 2021-09-14 12:36
sveni have some patches to the tps6598x driver and want to make sure i didn't break anything #asahi · 2021-09-14 12:35
sventhe apple m1 :D#asahi · 2021-09-14 12:16
svenanyone with a imx8mq-librem5 (probably this Librem 5 phone i guess) and/or any other board with a TI TPS6598x chip here who knows how to boot a custom kernel on those?#asahi · 2021-09-14 10:03
svenit's also not just an arm concept#asahi · 2021-09-14 10:03
svenhttps://en.wikipedia.org/wiki/Message_queue "In computer science, message queues and mailboxes are software-engineering components typically used for inter-process communication (IPC), or for inter-thread communication within the same process."#asahi · 2021-09-12 16:44
sventrue. i guess uboot could just reinitialize communication with SMC at that point and send the shutdown command#asahi · 2021-09-12 14:47
svenshutdown may a bit tricky. it requires talking to the SMC co-processor which can't easily be multiplexed between the os and u-boot. and the os will probably need to talk to SMC for e.g. enabling wifi #asahi · 2021-09-12 07:51
svenalyssa: :<#asahi · 2021-09-11 16:38
svencan you try to see if you can break charging when you only disable interrupts in one of those two?#asahi · 2021-09-11 16:38
svenpipcet[m]: so it looks like this tps USB PD chip has _two_ i2c buses and with that also two independent interrupt controllers. i suspect one of them is connected to the main CPU while the other is connected to the SMC#asahi · 2021-09-11 16:19
svenyeah#asahi · 2021-09-11 16:12
svencould also be some internal flash i guess if it has to come up before SecureROM#asahi · 2021-09-11 16:10
svenhm, good point#asahi · 2021-09-11 15:27
svenhuh, does anyone know where the SMC firmware is stored? can't find it in the ipsw or in the preboot volume#asahi · 2021-09-11 13:03
sventhe fake-iommu that really just calls back into the main kext? :D#asahi · 2021-09-11 13:02
svenhah :D#asahi · 2021-09-11 13:00
sveni don't have a strong opinion regarding that separate rtkit node fwiw#asahi · 2021-09-11 13:00
sventhanks, that's good to know.#asahi · 2021-09-11 12:58
sven:>#asahi · 2021-09-11 12:58
sveni don't even know about all blocks that _currently_ use rtkit#asahi · 2021-09-11 12:56
sveni dunno#asahi · 2021-09-11 12:56
svenj_ey: oh, yep. ofc!#asahi · 2021-09-11 12:55
svenwhich is what's on the list + alyssa's review comments :-)#asahi · 2021-09-11 12:54
svenyup :D#asahi · 2021-09-11 12:54
svenSMC is a single rtkit channel#asahi · 2021-09-11 12:54
svenuh, no#asahi · 2021-09-11 12:54
svenyup#asahi · 2021-09-11 12:53
svenyes. so if we have multiple nodes that need to talk to difference rtkit channels we need that node#asahi · 2021-09-11 12:52
svenrepresenting firmware in DT as a separate node. Perhaps something like:"#asahi · 2021-09-11 12:52
svenfirmware as separate nodes in DT. There's certainly precedent for #asahi · 2021-09-11 12:52
sven"I expect you'd end up representing the low-level mbox HW and the remote #asahi · 2021-09-11 12:52
svenalyssa: see https://lore.kernel.org/all/550C7534.8070100@wwwdotorg.org/#asahi · 2021-09-11 12:52
svennot really sure which of those i prefer#asahi · 2021-09-11 12:52
sventhe other alternative is that separate rtkit node that would handle the rtkit stuff and that the nvme driver could reference #asahi · 2021-09-11 12:51
sventhere is at least the SEP which will also use the mailbox HW but doesn't speak rtkit at all#asahi · 2021-09-11 12:51
sventhat's one alternative, yes#asahi · 2021-09-11 12:49
svenyeah, i'm not really sure how those will look like yet either. two two alternative i see is to have a separate rtkit node (like https://lore.kernel.org/all/550C7534.8070100@wwwdotorg.org/ suggested for the raspberry pi case) or to have the rtkit handling be part of the nvme driver (shared as some library)#asahi · 2021-09-11 12:41
sventhe other two irqs are also symmetric fwiw. i think they literally just hooked up the same HW block to both processors #asahi · 2021-09-11 12:38
sveni copy/pasted them from marcan's original m1n1 tracer i think