00:48 <chadmed> i will install the branch on my server to confirm then. it definitely 100% does not exist on the studio though

00:48 <chadmed> both j314 and j415 have it though

00:49 <chadmed> the set of common keys seems to be rather small. i doubt we can avoid sku-specific hwmon keys for very long

01:07 <chadmed> ok yeah TW0P exists on the m2 pro mini

01:07 <chadmed> interesting

09:46 <chadmed> okay i think we're 99% of the way to something workable for hwmon if anyone has any feedback

09:47 <chadmed> https://github.com/chadmed/linux/tree/asahi-hwmon-next

09:47 <chadmed> im not a fan of how fragmented the devicetree stuff needs to be but id rather deal with a bit of an ugly dt than have loads of "could not get key" errors polluting folks' dmesg

09:57 <jannau> maybe we should do chassis specific includes? or just include key specific includes like '#include hwmon-temp-tw0p.dtsi`. that avoids duplicating the key info

10:12 <chadmed> i toyed with the idea of an hwmon-desktop.dtsi but since tw0p is on the minis but not the studios (and who even knows what is going on with the pro :p) that didnt really make a lot of sense to me. there doesnt really seem to be any common thread

10:12 <chadmed> i think we need to play with more keys across more machines to have a better idea of what is actually common and what isnt. if its just a few useless/anciliary keys that arent shared then we can just not even bother with them

10:42 <jannau> chadmed: I was thinking of hwmon-mini.dtsi / hwmon-studio.dtsi instead of desktop

10:46 <chadmed> yeah that would probably work, again assuming theres not too much else that is divergent. im kinda worried that the mac pro will introduce even more nonsense that will necessitate a -desktop in between -common and -mini/-studio anyway

10:50 <jannau> I wouldn't worry about the pro

10:56 <chadmed> heh