torez has quit [Quit: torez]
<digetx> tagr: any updates on the memory bw patchset? the display controller doesn't work well without it. I saw that you sent out the 5.14 drm PR, making me wonder what happened to v18
DavidHeidelberg has joined #tegra
maxim[m] has joined #tegra
digetx has quit [Ping timeout: 272 seconds]
digetx has joined #tegra
lahvuun- has quit [Ping timeout: 252 seconds]
torez has joined #tegra
lahvuun has joined #tegra
<digetx> m4t: pgwipeout was trying to use CC2 gpio for the nct1008 interrupt, but the CC2 pin is used by I2C, so it's wrong gpio
<m4t> hmm, do we know the correct one?
<digetx> interestingly, nexus7 schematics also has wrong CC2 gpio connected to TEMP_ALERT on one page and S3/S6 on other page, the S3 works
<digetx> that interrupt is very optional, kernel doesn't make use of it other than to print a warning message when temperature goes out of range, I wanted to let you know about it
<m4t> there was something where that message kept being repeated over and over again
<digetx> it's either connected to a different gpio on ouya or not connected at all
<digetx> the non-stopping messages are the separate driver issue, I'll send patch later today to switch lm90 to use edge trigger instead of level
<m4t> maybe unrelated but its like the interrupt was never cleared
<m4t> oh
<digetx> the CC2 is jumping 1/0 non-stop, I think
<m4t> i2c clock or something?
<digetx> ah, it's not i2c, but i2s
<digetx> nvidia,function = "i2s4" for pcc2
<digetx> although, i2s4 not used on ouya
<m4t> originated there?
<digetx> maybe
<digetx> the cc2 also doesn't stop to trigger as interrupt for both low/high trigger levels on nexus7
<digetx> the lm90 doesn't support clearing interrupt, it just checks the temperature status on interrupt
<digetx> technically all those device-trees that use IRQ_TYPE_LEVEL_LOW are incorrect, it should be IRQ_TYPE_EDGE_FALLING
<m4t> makes sense
_whitelogger has joined #tegra
aat596[m] has joined #tegra
gouchi has joined #tegra
<digetx> m4t: have you updated alpine?
<m4t> no, was there a release?
<digetx> yes
<m4t> okay, i will try to tonight
<digetx> I tried to enable tegra-hda in nexus7 DT and see that pulseaudio autoloads the new ucm
<digetx> but that's on gentoo
<digetx> i.e. the most recent ucm + alsalib
gouchi has quit [Remote host closed the connection]
<digetx> seems alpine 3.14 has a fresh alsa-lib, but not fresh alsa-ucm-conf, so you will need to pull recent ucm manually
<m4t> just using alsa directly on the ouya
<m4t> alpine is really eager to remove all system packages, hah https://paste.ee/p/a0aGj#rm7WemuLgSb1Qs1hDtLEXGy3pJBgLJU8
<m4t> (it's because i didn't do an apk update beforehand)
<m4t> still alsaucm is syntax 3. i can try downgrading the ver of the ouya stuff again...
<m4t> it seems pretty broken/out of sync anyways, it only looks at virt.conf.d (hard-coded in alsa, i guess):
<m4t> open("/usr/share/alsa/ucm2/conf.virt.d", O_RDONLY|O_LARGEFILE|O_CLOEXEC|O_DIRECTORY) = -1 ENOENT (No such file or directory)
<m4t> but that dir doesn't exist in the alsa-ucm-conf package....
<m4t> okay, so i cloned the repo, mv alsa-ucm-conf/ucm2 /usr/share/alsa; mv virt.conf.d virt.conf.d.bak; mv conf.d virt.conf.d; ln -s virt.conf.d/tegra; ln -s virt.conf.d/tegra-hda;
<m4t> ouya:/usr/share/alsa/ucm2# alsaucm listcards
<m4t> 0: tegra-hda
<m4t> what a PITA