Add test script to validate USB UAC by achauras-qcom · Pull Request #266 · qualcomm-linux/qcom-linux-testkit

achauras-qcom · 2026-02-01T21:35:08Z

The shell script verifies the enumeration of USB Audio Devices connected to DUT.

smuppand

Commit ordering / path inconsistency (important for clean history)

Create files directly in Runner/suites/Kernel/Baseport/USB/usb_uac/ from patch 1 onward, and drop patch 4/4 entirely.
Alternative:
Move patch 4/4 earlier (as 1/4), then add script/README/YAML into the final location.

smuppand · 2026-03-02T16:34:56Z

+audio_device_count=$(
+  for f in /sys/bus/usb/devices/*/bInterfaceClass; do
+    [ -r "$f" ] || continue
+    if grep -qx '01' "$f"; then


Validate more than bInterfaceClass == 01

smuppand · 2026-03-02T16:35:25Z

+# Count uniques devices with bInterfaceClass = 01 (UAC) under /sys/bus/usb/devices
+audio_device_count=0
+log_info "=== USB Audio device Detection ==="
+audio_device_count=$(


Add ALSA/device-node checks (/dev/snd, /proc/asound/cards, aplay -l, arecord -l where available)
Print detected UAC device details (VID:PID, product, device path)

smuppand · 2026-03-02T16:35:53Z

+log_info "=== Test Initialization ==="
+
+# Check if grep is installed, else skip test
+deps_list="grep sed sort wc"


Add missing dependency tr

smuppand · 2026-03-02T16:36:37Z

+  done 2>/dev/null | sed 's/:.*$//' | sort -u | wc -l | tr -d '[:space:]'
+  )
+
+log_info "Number of USB audio devices found: $audio_device_count"


Distinguish playback-only vs capture-only devices and also log bound driver info from sysfs

smuppand · 2026-03-02T16:37:16Z

+
+- Connect USB Audio peripheral(s) to USB port(s) on DUT.
+- Only applicable for USB ports that support Host Mode functionality. 
+- USB Audio peripherals examples: USB headset, microphone, sound card, etc. 


Improve README to clarify exact validation scope

smuppand · 2026-03-02T16:38:00Z

+    echo "$TESTNAME PASS" > "$RES_FILE"
+    exit 0
+else
+    log_fail "$TESTNAME : Test Failed - No 'USB Audio Device' found"


Consider whether “no UAC device attached” should be FAIL or SKIP

achauras-qcom · 2026-03-31T12:47:35Z

Output for UAC device connected:
root@rb3gen2-core-kit:/var# ./run.sh
[INFO] -----------------------------------------------------------------------------------------
[INFO] -------------------Starting usb_uac Testcase----------------------------
[INFO] === Test Initialization ===
[INFO] === USB Audio device Detection ===
[INFO] Number of USB audio devices found: 1
[INFO] === Enumerated USB Audio Devices ===

DEVICE VID:PID PRODUCT

1-1 04e8:a05e Samsung USB C Earphones

[INFO] ALSA cards (/proc/asound/cards):
[INFO] 0 [QCS6490RB3Gen2 ]: qcs6490 - QCS6490-RB3Gen2
[INFO] QCS6490-RB3Gen2
[INFO] 1 [Earphones ]: USB-Audio - Samsung USB C Earphones
[INFO] Samsung Samsung USB C Earphones at usb-xhci-hcd.4.auto-1, full speed
[INFO] Number of ALSA USB sound cards: 1
[INFO] ALSA card 1 device nodes present: playback capture
[PASS] usb_uac : Test Passed - USB Audio device(s) detected and ALSA device nodes present

smuppand

squash it to one commit.

smuppand · 2026-04-01T15:20:28Z

+
+# Default result file (works even before functestlib is available)
+# shellcheck disable=SC2034
+RES_FILE="$SCRIPT_DIR/${TESTNAME}.res"


current default is ./${TESTNAME}.res, so early SKIP paths before cd "$test_path" can write the result file into an unexpected working directory.

Skip paths before cd "$test_path" could reliably write result file in "$SCRIPT_DIR", please correct me if my understanding is wrong. Does default result file need to be changed to "./${TESTNAME}.res" instead of "$SCRIPT_DIR/${TESTNAME}.res"?

Skip paths before cd "$test_path" could reliably write result file in "$SCRIPT_DIR", please correct me if my understanding is wrong. Does default result file need to be changed to "./${TESTNAME}.res" instead of "$SCRIPT_DIR/${TESTNAME}.res"?

Yes, your understanding is correct.

Using:

RES_FILE="$SCRIPT_DIR/${TESTNAME}.res"

is better for the early SKIP paths before cd "$test_path" because the script may be launched from any working directory. If we used:

RES_FILE="./${TESTNAME}.res"

then early failures such as missing init_env could write the result into the caller's current directory instead of the testcase directory.

Using RES_FILE="$SCRIPT_DIR/${TESTNAME}.res" for early skip paths in the script

smuppand · 2026-04-01T15:22:56Z

+    sys="/sys/bus/usb/devices/$dev"
+    vid=$([ -r "$sys/idVendor"  ]  && tr -d '[:space:]' < "$sys/idVendor"  || echo -)
+    pid=$([ -r "$sys/idProduct" ]  && tr -d '[:space:]' < "$sys/idProduct" || echo -)
+    if [ -r "$sys/product" ]; then


when a UAC interface enumerates but ALSA integration is incomplete, we still lose useful debug context in CI logs. Add a DRIVER column and populate it from the relevant interface driver symlink in sysfs.

DEVICE VID:PID DRIVER PRODUCT 1-1 04e8:a05e snd-usb-audio Samsung USB C Earphones

Added driver info as well for each UAC device.

smuppand · 2026-04-01T15:23:51Z

+        missing_nodes=1
+    fi
+    if [ "$has_pcm_p" -ne 1 ] && [ "$has_pcm_c" -ne 1 ]; then
+        log_fail "Missing ALSA PCM device(s) for card $c (no playback or capture node found)"


tighten PASS to require all detected UAC-backed ALSA cards to have playback/capture nodes, or
at least log an explicit ratio such as usable ALSA USB cards: X/Y so partial failures are visible.

Added missing nodes info for each UAC device as part of debug logs and also logging explicit ratio of usable ALSA USB cards.

The shell script verifies the enumeration of USB Audio Class devices. Signed-off-by: Aanchal Chaurasia <achauras@qti.qualcomm.com>

achauras-qcom requested a review from smuppand February 2, 2026 12:10

achauras-qcom force-pushed the feature/usb-uac branch 2 times, most recently from 6877bdd to 9f1040f Compare February 17, 2026 11:41

smuppand requested changes Feb 21, 2026

View reviewed changes

achauras-qcom force-pushed the feature/usb-uac branch from 9f1040f to 402263a Compare February 27, 2026 08:51

smuppand requested changes Mar 2, 2026

View reviewed changes

achauras-qcom force-pushed the feature/usb-uac branch from 402263a to 63b743c Compare March 31, 2026 12:03

github-advanced-security AI found potential problems Mar 31, 2026

View reviewed changes

Comment thread Runner/suites/Kernel/Baseport/USB/usb_uac/run.sh Fixed

Comment thread Runner/suites/Kernel/Baseport/USB/usb_uac/run.sh Fixed

achauras-qcom force-pushed the feature/usb-uac branch from 63b743c to 2431fc7 Compare March 31, 2026 12:41

smuppand requested changes Apr 1, 2026

View reviewed changes

Add test script to validate USB UAC

eaf38ac

The shell script verifies the enumeration of USB Audio Class devices. Signed-off-by: Aanchal Chaurasia <achauras@qti.qualcomm.com>

achauras-qcom force-pushed the feature/usb-uac branch from 2431fc7 to eaf38ac Compare May 29, 2026 06:36

Conversation

achauras-qcom commented Feb 1, 2026

Uh oh!

smuppand left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

achauras-qcom commented Mar 31, 2026

DEVICE VID:PID PRODUCT

Uh oh!

smuppand left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

achauras-qcom Apr 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

achauras-qcom Apr 30, 2026 •

edited

Loading