<digetx> m4t: you need to use the latest grate-kernel to get proper interrupt trigger
<m4t> hmm
<digetx> please apply https://dpaste.com/8G4CHPVBT
<m4t> apply that to the OLD kernel (2021/05/20) ?
<m4t> i cannot use usb audio on the latest so i just rebuilt the old one
<digetx> you can use old, but you'll get interrupt storm on trigger
<digetx> it shouldn't trigger by default
<m4t> is that sufficient to test, then?
<digetx> at first we need to fix interrupt, then we can check it
<digetx> you can use old kernel for that too
<m4t> i'll just rebuild the latest and unplug usb audio for a minute. do i still need both patches with the latest git?
<digetx> yes, both needed
<m4t> ok
<digetx> it actually could be easier to test using older kernel since it has warning messages that are turned into debug messages now, but you can enable them manually if needed
<m4t> ok
<digetx> if interrupt will work properly at boot, then use this to trigger it:
<digetx> echo 50000 > /sys/devices/soc0/7000d000.i2c/i2c-0/0-004c/hwmon/hwmon4/temp2_min
<m4t> i think it idles above 50c
<m4t> nope
<m4t> https://imgur.com/a/KAWOUca will just 'openssl speed' or something
<m4t> what should i expect if it triggers the interrupt?
<m4t> something in dmesg?
<digetx> /proc/interrupts will bump and you will get message in dmesg if you'll enable those debug messages
<m4t> gotcha
<m4t> yeah i enabled them
<m4t> will let you know in a minute. rebooting
<m4t> not correct sysfs path. /sys/devices/soc0/7000d000.i2c/i2c-1/1-004c/hwmon/hwmon2/temp2_min
<digetx> find /sys | grep hwmon
<digetx> nice
<m4t> yep
<digetx> I'll add yours t-b, thank you
<m4t> cool
<m4t> going to downgrade so i can keep listening to music heh
<m4t> oh hrm, temp2_min not temp2_max :P
<m4t> so it should've triggered < 50c
<digetx> it did
<m4t> nct1008_2: +47.2°C (low = +42.0°C, high = +60.0°C)
<digetx> nct1008_2: +45.8°C (low = +50.0°C, high = +60.0°C) ALARM (LOW)
<m4t> yes
<m4t> just the whole openssl speed thing was unnecessary i think
<m4t> :D
<digetx> :)
<digetx> won't hurt to double check the whole pinmux, pgwipeout was assuring that it is correct, but seems not entirely
<m4t> lots of pins to check
<m4t> i did run into the mmc thing on the initial kernel inclusion
<m4t> in hindsight i wish i would've tested that beforehand instead of waiting for it to be merged
<digetx> it also could be difficult to notice incorrect pinmux, it may result in odd occasional failures
indy has quit [Read error: Connection reset by peer]
indy has joined #tegra
marvin24 has quit [Ping timeout: 252 seconds]
marvin24 has joined #tegra
gouchi has joined #tegra
marvin24 has quit [Ping timeout: 244 seconds]
marvin24 has joined #tegra
crabbedhaloablut has quit [*.net *.split]
crabbedhaloablut has joined #tegra
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #tegra
crabbedhaloablut has quit [Ping timeout: 244 seconds]
crabbedhaloablut has joined #tegra
crabbedhaloablut has quit [Quit: No Ping reply in 180 seconds.]
crabbedhaloablut has joined #tegra
lahvuun has quit [Ping timeout: 258 seconds]
lahvuun has joined #tegra
gouchi has quit [Remote host closed the connection]
pangelo[m] has joined #tegra
gouchi has joined #tegra
gouchi has quit [Remote host closed the connection]
gouchi has joined #tegra
gouchi has quit [Remote host closed the connection]
gouchi has joined #tegra
gouchi has quit [Remote host closed the connection]