#asahi-dev · 2025-09-26 11:58
jannauauscyber_: you have to define TARGET to T8132 for BRINGUP#asahi-dev · 2025-09-26 11:58
jannauno, I suspect smc reboots because due to charging issues#asahi-dev · 2025-09-26 11:57
jannaucan you try with power over magsafe connected#asahi-dev · 2025-09-26 11:56
jannauI don't think the reboots are caused by the watchdog#asahi-dev · 2025-09-26 11:55
jannaudo you have the magsafe charging cable connected?#asahi-dev · 2025-09-26 11:54
jannauwhich device are you trying to get running?#asahi-dev · 2025-09-26 11:51
jannauare you now using a apple silicon device with linux?#asahi-dev · 2025-09-26 11:50
jannauno reboots with with a normal build with working usb after more than 3 minutes though#asahi-dev · 2025-09-26 11:49
jannauusb is not essential#asahi-dev · 2025-09-26 11:49
jannauyes#asahi-dev · 2025-09-26 11:48
jannauit's a mode which disables most non-essential feature intended for bringup of new devices#asahi-dev · 2025-09-26 11:48
jannaugit grep BRINGUP#asahi-dev · 2025-09-26 11:42
jannauBRINGUP build on base M4 mac mini (26.0) does not reboot#asahi-dev · 2025-09-26 10:14
jannau.../nub-spmi0/pmu-main has many info-fault_name-* properties. that could possibly identify the reason for the reboot. I don't know how easy it'll be to access them on m4#asahi-dev · 2025-09-26 10:10
jannaudo you have a iomon.poll output close (single digit seconds) to the reboot?#asahi-dev · 2025-09-26 09:40
jannaumy mac mini m2 pro with tahoe beta does not seem to reboot. Using a m1n1 bringup build#asahi-dev · 2025-09-26 08:49
jannausame, that's why I asked to reset CUR_TIME for all 3 know watchdogs#asahi-dev · 2025-09-26 08:48
jannauthere is also regmonitor to automatically diff reg spaces over time. that could identify if there are now more watchdogs with increemnting time#asahi-dev · 2025-09-26 08:46
jannaua dump of the first the watchdog block might be helpful#asahi-dev · 2025-09-26 08:45
jannaudoews it still reboot if you write 0 to 0x00, 0x10, 0x20 every 5 seconds#asahi-dev · 2025-09-26 08:18
jannausee `udev/80-m1n1.rules`. with that you get "/dev/m1n1"#asahi-dev · 2025-09-26 08:16
jannauit looked like restarts from my BRINGUP builds. it sits there for 30 seconds or a minute and then reboots#asahi-dev · 2025-09-26 08:11
jannauu.adt["/arm-io/wdt"].get_reg(0)[0] to get the translated 1st register value from the wdt node#asahi-dev · 2025-09-26 08:06
jannaualso the adt python and c (rust) code does this if you use get_reg()#asahi-dev · 2025-09-26 08:03
jannauif the value is in [bus_addr, bus_addr + size] add parent_addr#asahi-dev · 2025-09-26 07:55
jannau/arm-io/ranges#asahi-dev · 2025-09-26 07:53
jannaueither here or in #asahi-re#asahi-dev · 2025-09-26 07:51
jannauchadmed: why are "AC Input Voltage / Current" in hwmon-common.dtsi? At least based on the name they make no sense on laptops#asahi-dev · 2025-09-25 21:07
jannauwhy does hwmon use HWMON_I_* for voltage#asahi-dev · 2025-09-25 20:33
jannausent#asahi-dev · 2025-09-25 20:16
jannauwe do not care that much and there are hopefully not many upstream users (if at all)#asahi-dev · 2025-09-25 20:12
jannauI'm also surprised it only fails occasionally#asahi-dev · 2025-09-25 20:12
jannauI'll send a fix probably too late for v6.17 though#asahi-dev · 2025-09-25 20:10
jannaumacsmc.c never calls mutex_init()#asahi-dev · 2025-09-25 20:04
jannaualso afaik core isn't supposed to probe childrens before the their parent's probe finished#asahi-dev · 2025-09-25 20:03
jannauit's not unset drvdata#asahi-dev · 2025-09-25 20:00
jannauwith a compatible that matches apple-dart?#asahi-dev · 2025-09-25 19:47
jannauchadmed: it's the reason why I added the __SMC_KEY macro in the downstream driver. I think gcc had this issue always#asahi-dev · 2025-09-25 19:45
jannauI think if we add compatibles and of_match tables driver core could probe them as well#asahi-dev · 2025-09-25 19:24
jannauI'm seing this https://paste.debian.net/1398135/ and saw essentially the same with smc-hid before#asahi-dev · 2025-09-25 19:22
jannauis it possible that trhe sub drivers are probed before the smc driver set its driver data?#asahi-dev · 2025-09-25 19:13
jannauthe keys aren't fully though but in the case of hwmon that's delegated directly into the DT#asahi-dev · 2025-09-25 18:56
jannaudo we need soc specific compatibles for the smc subnodes?#asahi-dev · 2025-09-25 18:42
jannauaren't the sub driver probed via mfd cells?#asahi-dev · 2025-09-25 18:42
jannauI think we need smc subnodes with their own compatibles on apple silicon#asahi-dev · 2025-09-25 18:28
jannauyes, but it's not clear/constant what the individual keys are. you can't (shouldn't) just expose all because at least on apple silicon there are keys either reporting constant 0 or bogus values#asahi-dev · 2025-09-25 18:23
jannauon apple silicon side DT is preferred because it means that we do not have to modify the driver when a new model arrives. just the DT which we have to add anyway#asahi-dev · 2025-09-25 18:22
jannauplease reply now to the v2 hwmon driver patch that there is a use case for non-DT macsmc HW mon support#asahi-dev · 2025-09-25 18:20
jannauI don't see how you can hardcode the keys as they differ per model / soc (on apple silicon side)#asahi-dev · 2025-09-25 18:19
jannauno, that would not be ok