Add PipeWire support to AudioRecord and AudioPlayback tests

[tmoida]

• Updated AudioRecord and AudioPlayback scripts to support both PulseAudio and PipeWire
• Added AUDIO_BACKEND variable for backend selection
• Updated README files with usage instructions for both backends
• Modified LAVA test plan to run tests with both PulseAudio and PipeWire

[smuppand]

@tmoida Could you please squash the commits into a single one?

[tmoida]

Hi @smuppand ,
I have squashed the commits into a single one as requested. Kindly review it and let me know if any further changes are needed.

[smuppand]

few chnages needed like pre-scan dmesg (use common helpers) -> Run playback (possibly loop) -> post-scan dmesg fir any potential audio-related dmesg messages detected.

better to add a daemon check which prevents false failures when the server isn't running

loops + timeout - Lets you simulate longer playback without hanging CI.

[tmoida]

Hi @smuppand,
I've updated the Audio test scripts and documentation as per the feedback. Key improvements include:

- Added daemon checks for both PulseAudio and PipeWire backends
- Replaced eval with safer command execution using sh -c
- Introduced support for environment variables like PLAYBACK_VOLUME, PLAYBACK_TIMEOUT, PLAYBACK_LOOPS, RECORD_TIMEOUT, and RECORD_LOOPS
- Implemented pre/post dmesg scanning using get_kernel_log and scan_dmesg_errors
- Updated both README files to reflect the new features and usage instructions

Please let me know if there is anything else that needs to be addressed.

[smuppand]

@tmoida , please squash your commits.

[tmoida]

Hi @smuppand,

I've squashed the commits and fixed the Shell Check warning by using the loop variable. Please let me know if there is anything else that needs to be addressed.

Also. I have validated these scripts on Yocto builds, and they work fine. However, on Mainline (Nightly sanity) builds, they are being skipped due to a missing timeout binary. I wanted to check: will the timeout binary be included in future builds, or should I update the script to avoid using it?

[smuppand]

Hi @smuppand,

I've squashed the commits and fixed the Shell Check warning by using the loop variable. Please let me know if there is anything else that needs to be addressed.

Also. I have validated these scripts on Yocto builds, and they work fine. However, on Mainline (Nightly sanity) builds, they are being skipped due to a missing timeout binary. I wanted to check: will the timeout binary be included in future builds, or should I update the script to avoid using it?

You can use the library function run_with_timeout() if the build does not include the timeout utility.

[tmoida]

Hi @smuppand,

Thanks for the suggestions!

I've updated the loop logic to handle early exits cleanly and added clearer return handling to distinguish between success and timeout cases. Also, I've replaced timeout with run_with_timeout() as a fallback to ensure compatibility on builds where the timeout binary is missing.

Please let me know if there is anything else that needs to be addressed.

[smuppand]

@tmoida Please update the https://github.com/qualcomm-linux/qcom-linux-testkit/blob/main/Runner/plans/meta-ar-ci-premerge.yaml to include the changes that involve launching or adding any tests.