#asahi-dev · 2021-11-12 20:59
kettenisit isn't inconceivable that they implemented a "proper" reset path for the new machines instead of abusing the watchdog timer#asahi-dev · 2021-11-12 20:17
kettenislooks like the physical address of a register to me ;)#asahi-dev · 2021-11-12 19:35
kettenisfair enough#asahi-dev · 2021-11-12 19:33
kettenisis the clock enable/disable code really necessary?#asahi-dev · 2021-11-12 19:24
kettenisthe reboot driver in the linux-sandcastle tree does effectively the same thing as the sven's new driver#asahi-dev · 2021-11-12 19:08
kettenisthat is the case in proper device trees as well#asahi-dev · 2021-11-12 19:07
kettenissometimes it looks as if the 2nd cell is some sort of flag instead of an interrupt number#asahi-dev · 2021-11-12 18:55
kettenismaybe the more advanced options aren't present on the older SoCs#asahi-dev · 2021-11-12 18:54
kettenisfrom what I've seen, older phone SoCs have the same interface#asahi-dev · 2021-11-12 18:54
kettenisregarding the binding, I don't think it makes a lot of sense to call this "wdt2"#asahi-dev · 2021-11-12 18:52
kettenisstart simple#asahi-dev · 2021-11-12 18:50
kettenisit is#asahi-dev · 2021-11-12 18:46
kettenisanyway, I'm somewhat surprised nobody implemented a linux driver for the watchdog yet#asahi-dev · 2021-11-12 18:25
kettenisheh, I actually find the chime useful as feedback when I'm sitting in my lazy chair and I'm resetting the mini on my desk#asahi-dev · 2021-11-11 12:06
kettenisthe PCI bus binding has revision 2.1, but the interrupt mapping "recommended practice" is 0.9 and labelled "Unapproved DRAFT"#asahi-dev · 2021-11-11 11:58
kettenisto be fair, what maz did for the apple pcie kinda extrapolates the spec as well#asahi-dev · 2021-11-11 11:54
kettenisugh, yes, the way the interrupts are described for everything that maps to the "pa-pxp" interrupt controller is totally busted#asahi-dev · 2021-11-10 15:03
kettenisflushing the disk cache is typically only done upon reboot or when the device is put into a deep sleep state#asahi-dev · 2021-11-10 15:02
kettenisit might still be cached by the disk itself#asahi-dev · 2021-11-10 15:02
kettenisthat still doesn't guarantee the data actually lands on stable storage#asahi-dev · 2021-11-10 15:01
kettenisthis is why you have to actually type sync three times for it to work ;)#asahi-dev · 2021-11-10 15:01
kettenisand sync(2) only makes the kernel push out dirty buffers to disk asynchronously#asahi-dev · 2021-11-10 15:00
kettenistraditionally alls sync(8) does is call sync(2)#asahi-dev · 2021-11-10 11:35
kettenisfdisk did read the protective mbr alright#asahi-dev · 2021-11-10 10:29
kettenisj_ey: yes, in principle, but I think iit would be ok for m1n1 to be "ahead" of the ones in the Linux repository from time to time#asahi-dev · 2021-11-10 10:28
kettenismarcan: i think it is time for another nudge for those#asahi-dev · 2021-11-10 10:27
kettenisbut what we really need is approved pwrmgr bindings before we start curating device trees#asahi-dev · 2021-11-10 10:26
ketteniswe should just have blessed device trees in the m1n1 repository since the device tree that actually gets used will come from there#asahi-dev · 2021-11-10 10:25
kettenishaving the dts in the linux repo really doesn't make a lot of sense for us#asahi-dev · 2021-11-10 08:35
kettenisbut maybe they use the PCIe endpoint controller#asahi-dev · 2021-11-10 08:34
kettenismarcan: the (usual) designware mmc controller isn't a standard SDHC one, so that is unlikely#asahi-dev · 2021-11-09 20:29
kettenis(just something that caught my eye when I watched today's youtube stream)#asahi-dev · 2021-11-09 20:28
kettenisthe tell-tale signs of some Synopsys DesignWare "IP"#asahi-dev · 2021-11-09 20:28
kettenis00000005c1800500 3135302a 67612a2a ...#asahi-dev · 2021-11-09 12:03
kettenisis there actually something to control in that area?#asahi-dev · 2021-11-09 11:55
kettenisBMIC?#asahi-dev · 2021-11-09 11:52
kettenisthe spmi pmu has a similar issue of course#asahi-dev · 2021-11-09 11:50
kettenisthe hard problem is to come up with a meaningful subdividion ;)#asahi-dev · 2021-11-09 11:46
kettenisI think there are examples in Linux for "MFD"s that don't have a node in the DT for each separate function#asahi-dev · 2021-11-09 11:44
kettenisyeah#asahi-dev · 2021-11-09 11:36
kettenisbut as stated above, these all depend on the same shared memory#asahi-dev · 2021-11-09 11:34
kettenistraditionally those are handled by separate drivers#asahi-dev · 2021-11-09 11:33
kettenisit provides quite a wide variety of functionality, i.e. GPIO, powerdown, sensors#asahi-dev · 2021-11-09 11:12
kettenisI fear it depends on how the SMC functionality is going to be split out over multiple drivers and whether that needs multiple DT nodes#asahi-dev · 2021-11-09 11:09
ketteniss/halt/half/#asahi-dev · 2021-11-09 11:09
kettenisindeed; defenitely more than a memory halt-time ago for me ;)#asahi-dev · 2021-11-09 11:06
kettenisgetting the DT bindings sorted out will take some back and forth still#asahi-dev · 2021-11-09 11:04
kettenisdon't want to tell you what to work on, but the rtkit stuff is a fairly basic building block, hint, hint#asahi-dev · 2021-11-09 10:11
kettenismarcan: that sdhc/pcie behaviour is really weird#asahi-dev · 2021-11-08 10:41
kettenisj_ey: so I think that is a valid packet, but one that doesn't actually contains a "message"