Hello, we have noticed that the “NvBufferTransform” function, which in theory uses the VIC HW, has an inconsistent performance, sometimes taking as much as 2x time to do the same conversion.
Time taken by NvBufferTransform scaling a 2800*1500 picture:
Conversion time: 7340
Conversion time: 2759
Conversion time: 2731
Conversion time: 3930
Conversion time: 3865
Conversion time: 7266
Conversion time: 7322
Any ideas why is this happening?
Hi,
We enable DFS of VIC from r32.4.3. It gives better power consumption but if your loading is always high, suggest disable it. Please refer to
Hi,
Please excute the steps to run VIC in max clock and try again:
Disable runtime suspend of VIC
$ echo on > /sys/devices/13e10000.host1x/15340000.vic/power/control
Set userspace governor
$ echo userspace > /sys/devices/13e10000.host1x/15340000.vic/devfreq/15340000.vic/governor
Set max_freq
$ cat /sys/devices/13e10000.host1x/15340000.vic/devfreq/15340000.vic/available_frequencies
$ echo [max_freq_val] > /sys/devices/13e10000.host1x/15340000.vic/devfreq/15340000.vic/max_freq
Set targ…
Hi,
The VIC governor is configured by our boot init script “/etc/systemd/nv.sh”. You can modify the nv.sh script to set static max value for VIC clock.
Snippet of VIC configuration in /etc/systemd/nv.sh
case "${SOCFAMILY}" in
tegra186 | tegra194)
VIC_GOV_PARAM_PATH="/sys/devices/13e10000.host1x/15340000.vic"
VIC_DEV_PATH="${VIC_GOV_PARAM_PATH}/devfreq/15340000.vic"
if [ -e "${VIC_DEV_PATH}/available_governors" ]; then
…
1 Like