<kwizart>
digetx, also works under wayland (made a glmark2-wayland of 185 without much tearing)
<kwizart>
poweroff worked
<kwizart>
I think the features of tegra124 start to be interesting now that tearing is mostly gone and wayland works...The only missing feature would be video hw accel (probably with vaapi so it can have a chance to work under wayland)
<kwizart>
I don't think vaapi-tegra-driver can be used there as nvdec and vde are probably too different...
<kwizart>
cyndis, btw, do you have the tegra210 dts change for nvdec ? I plan to test it. I wonder if it works under wayland on X11 only ? (so I would need a recent xorg-server release).
<cyndis>
I don't, but it should be pretty easy to figure out. The base address is 0x54480000, then just need to fill in the power domain, clock, reset and iommu (TEGRA_SWGROUP_NVDEC)
<cyndis>
At least if you use vaapi-copy, I don't think the driver should have anything X11-specific, though I haven't tried it on wayland
<kwizart>
okay, thanks
<cyndis>
I think it's '-vo vaapi' that would activate the X11-specific path, so '-vo gpu' and '--hwdec=vaapi-copy'. Technically the code to support '--hwdec=vaapi' through dma-buf sharing should be in there but in my testing mesa/nouveau kept returning error codes when importing the dma-buf and I couldn't figure out why with reasonable effort at the time
<cyndis>
and yes, vde and nvdec are completely different :)
mshrimp_ has quit [Ping timeout: 260 seconds]
mshrimp has joined #tegra
camus has quit [Ping timeout: 260 seconds]
camus has joined #tegra
camus1 has joined #tegra
camus has quit [Ping timeout: 260 seconds]
camus1 is now known as camus
camus has quit [Quit: camus]
<mrkdir>
Hi, can anyone help me enable mclk (extperiph2) for imx219 with default tegracam sensor driver (imx219_v2.0.6)?
<mrkdir>
I can see the freq (24 mhz) configured in the device tree and the driver call camera_common_mclk_enable(s_data) but since no mclk output is there the i2c probe fails: "imx219_board_setup: error during i2c read probe (-121)"
<mrkdir>
Is it maybe just missing the clock refernce in the device tree?
camus has joined #tegra
pgwipeout[m] has quit [Quit: You have been kicked for being idle]
digetx has quit [Read error: Connection reset by peer]
digetx has joined #tegra
camus has quit [Quit: camus]
gouchi has joined #tegra
<digetx>
kwizart: thanks, I pushed update with patch that adds the missing USB interrupt to T124 DT, it should enable runtime PM for USB + re-added power-off patches (full set now); please check USB and power-off using the recent grate kernel
<digetx>
although, USB PM won't work on T124 because T124 PHY driver doesn't support it, I'll drop those patches
<kwizart>
digetx, hum, T124 PHY is the sameas T20/T30 ? I was wondering if some dev_info could be tuned into dev_dbg ? like in https://paste.centos.org/view/6ab2ce34 ?
<digetx>
that is USB2.0 PHY of microusb, XHCI doesn't use that PHY
<kwizart>
digetx, also I wonder if the missing USB interrupt is relevant for tegra210 also, I'm currently trying to find a regresion there and current 5.14 doesn't seems to access usb
<digetx>
yes, older T210 dtb is also affected
<digetx>
T186/192 too
<digetx>
194
digetx has quit [Read error: Connection reset by peer]
digetx has joined #tegra
gouchi has quit [Remote host closed the connection]
torez has quit [Quit: torez]
loki_val has quit [Remote host closed the connection]