# Verify Source: [https://docs.qualcomm.com/doc/80-70015-20/topic/bring-up.html](https://docs.qualcomm.com/doc/80-70015-20/topic/bring-up.html) The following workflow outlines the process to verify the function of the VPU driver. Figure : Workflow to verify the VPU driver Page-1 Run use cases Run use cases Verify if decode/encode is offloaded to VPU Verify if decode/encode is offloaded to VPU Verify if VPU driver is loaded Verify if VPU driver is loaded Boot up the driver Boot up the driver The commands and samples provided here enable you to verify the following: - VPU driver is successfully loaded - Decoding/encoding is offloaded to the VPU ## Verify if the VPU driver is successfully loaded The VPU driver is loaded as part of the kernel image. You can confirm whether the VPU driver is loaded successfully by executing either of the following commands: **Using lsmod command** 1. Run the following `lsmod` command on the device shell: lsmod | grep -i "iris"Copy to clipboard 2. To verify if the VPU driver is successfully loaded, review the sample output and ensure that an entry for `iris_vpu` is available under the Module column: Module Size Used by iris_vpu 585728 0Copy to clipboard **Using udevadm command** 1. Run the following command on the device shell and verify if the output shows `msm_vidc_decoder` and `msm_vidc_encoder` against the `ID_V4L_PRODUCT` tag. udevadm info -n /dev/video*Copy to clipboard 2. To verify whether the VPU is successfully loaded, review the following sample output: P: /devices/platform/soc@0/aa00000.video-codec/video4linux/video32 N: video32 L: 0 S: v4l/by-path/platform-aa00000.video-codec-video-index0 E: DEVPATH=/devices/platform/soc@0/aa00000.video-codec/video4linux/video32 E: DEVNAME=/dev/video32 E: MAJOR=81 E: MINOR=26 E: SUBSYSTEM=video4linux E: USEC_INITIALIZED=6690806 E: ID_V4L_VERSION=2 E: ID_V4L_PRODUCT=msm_vidc_decoder E: ID_V4L_CAPABILITIES=: E: ID_PATH=platform-aa00000.video-codec E: ID_PATH_TAG=platform-aa00000_video-codec E: ID_FOR_SEAT=video4linux-platform-aa00000_video-codec E: DEVLINKS=/dev/v4l/by-path/platform-aa00000.video-codec-video-index0 E: TAGS=:seat:uaccess: E: CURRENT_TAGS=:seat:uaccess: P: /devices/platform/soc@0/aa00000.video-codec/video4linux/video33 N: video33 L: 0 S: v4l/by-path/platform-aa00000.video-codec-video-index1 E: DEVPATH=/devices/platform/soc@0/aa00000.video-codec/video4linux/video33 E: DEVNAME=/dev/video33 E: MAJOR=81 E: MINOR=27 E: SUBSYSTEM=video4linux E: USEC_INITIALIZED=6686892 E: ID_V4L_VERSION=2 E: ID_V4L_PRODUCT=msm_vidc_encoder E: ID_V4L_CAPABILITIES=: E: ID_PATH=platform-aa00000.video-codec E: ID_PATH_TAG=platform-aa00000_video-codec E: ID_FOR_SEAT=video4linux-platform-aa00000_video-codec E: DEVLINKS=/dev/v4l/by-path/platform-aa00000.video-codec-video-index1 E: TAGS=:seat:uaccess: E: CURRENT_TAGS=:seat:uaccess:Copy to clipboard Note: To identify the device nodes, check for the `DEVNAME` tag. In the earlier example, the `/dev/video32` is for the VPU decoder node and `/dev/video33` is for the VPU encoder node. ## Verify if the decoding/encoding is offloaded to the VPU You can confirm if the video decoding or encoding is successfully offloaded to the VPU by doing the following: - Execute the following command as a loop: cat /proc/interrupts | grep "msm-vidc"Copy to clipboard - The following is the sample output that helps you verify whether the video decoding/encoding is offloaded to the VPU. Verify if the interrupt count from `msm-vidc` is increasing across any CPU when the use case is running: 253: 4 0 0 0 0 0 0 0 GICv3 206 Level msm-vidcCopy to clipboard Last Published: Oct 15, 2024 [Previous Topic Software](https://docs.qualcomm.com/bundle/publicresource/80-70015-20/topics/software.md) [Next Topic Sample applications](https://docs.qualcomm.com/bundle/publicresource/80-70015-20/topics/samples.md)