Changes in Makefile

55853cb8 - selftests/alsa: Fix circular dependency involving global-timer

Wed, 18 Dec 2024 02:59:31 +0000

selftests/alsa: Fix circular dependency involving global-timerThe pattern rule `$(OUTPUT)/%: %.c` inadvertently included a circulardependency on the global-timer target due to its inclusion in$(TEST_GEN_PROGS_EXTENDED). This resulted in a circular dependencywarning during the build process.To resolve this, the dependency on $(TEST_GEN_PROGS_EXTENDED) has beenreplaced with an explicit dependency on $(OUTPUT)/libatest.so. This changeensures that libatest.so is built before any other targets that require it,without creating a circular dependency.This fix addresses the following warning:make[4]: Entering directory 'tools/testing/selftests/alsa'make[4]: Circular default_modconfig/kselftest/alsa/global-timer <- default_modconfig/kselftest/alsa/global-timer dependency dropped.make[4]: Nothing to be done for 'all'.make[4]: Leaving directory 'tools/testing/selftests/alsa'Cc: Mark Brown Cc: Jaroslav Kysela Cc: Takashi Iwai Cc: Shuah Khan Signed-off-by: Li Zhijian Link: https://patch.msgid.link/20241218025931.914164-1-lizhijian@fujitsu.comSigned-off-by: Takashi Iwai List of files: /linux-6.15/tools/testing/selftests/alsa/Makefile

2a94a089 - selftest: alsa: check if user has alsa installed

Sun, 22 Sep 2024 22:58:18 +0000

selftest: alsa: check if user has alsa installedCurrently, if alsa development package is not installed on the user'ssystem then the make command would print a `pagefull` of errors. Inparticular one error message is repeated 3 times. This error is returnedby `pkg-config` and since it is not being handeled appropriately,repeated calls to `pkg-config` prints the same message again.This patch adds check for alsa package installation. If alsa is notinstalled, a short and consize error is returned. Also, it does notaffect the compilation of other tests.Signed-off-by: Abdul Rahim Reviewed-by: Shuah Khan Link: https://patch.msgid.link/20240922225824.18918-1-abdul.rahim@myyahoo.comSigned-off-by: Takashi Iwai List of files: /linux-6.15/tools/testing/selftests/alsa/Makefile

1026392d - selftests: ALSA: Cover userspace-driven timers with test

Tue, 13 Aug 2024 12:07:01 +0000

selftests: ALSA: Cover userspace-driven timers with testAdd a test for the new functionality of userspace-driven timers and thetool which allows us to count timer ticks in a certain time period. Thetest:1. Creates a userspace-driven timer with ioctl to /dev/snd/timer2. Starts the `global-timer` application to count the ticks of the timerfrom step 1.3. Asynchronously triggers the timer multiple times with some interval4. Compares the amount of caught ticks with the amount of trigger calls.Since we can't include and in onefile due to overlapping declarations, I have to split the test into twoapplications: one of them counts the amount of timer ticks in thedefined time period, and another one is the actual test which createsthe timer, triggers it periodically and starts the first app to countthe amount of ticks in a separate thread.Besides from testing the functionality itself, the test represents asample application showing userspace-driven ALSA timers API.Also, the timer test includes a test case which tries to create a timerwith invalid resolution (=0), and NULL as a timer info structure.Signed-off-by: Ivan Orlov Signed-off-by: Takashi Iwai Link: https://patch.msgid.link/20240813120701.171743-5-ivan.orlov0322@gmail.com List of files: /linux-6.15/tools/testing/selftests/alsa/Makefile

2032e61e - kselftest/alsa: Ensure _GNU_SOURCE is defined

Thu, 16 May 2024 15:27:33 +0000

kselftest/alsa: Ensure _GNU_SOURCE is definedThe pcmtest driver tests use the kselftest harness which requires that_GNU_SOURCE is defined but nothing causes it to be defined. Since theKHDR_INCLUDES Makefile variable has had the required define added let'suse that, this should provide some futureproofing.Fixes: daef47b89efd ("selftests: Compile kselftest headers with -D_GNU_SOURCE")Signed-off-by: Mark Brown Reviewed-by: Muhammad Usama Anjum Signed-off-by: Shuah Khan List of files: /linux-6.15/tools/testing/selftests/alsa/Makefile

10b98a4d - selftests: ALSA: Add test for the 'pcmtest' driver

Tue, 06 Jun 2023 19:32:54 +0000

selftests: ALSA: Add test for the 'pcmtest' driverThis test covers the new Virtual PCM Test Driver, including the capturing,playback and ioctl redefinition functionalities for both interleaved andnon-interleaved access modes. This test is also helpful as an usage exampleof the 'pcmtest' driver.We have a lot of different virtual media drivers, which can be used fortesting of the userspace applications and media subsystem middle layer.However, all of them are aimed at testing the video functionality andsimulating the video devices. For audio devices we have only snd-dummymodule, which is good in simulating the correct behavior of an ALSA device.I decided to write a tool, which would help to test the userspace ALSAprograms (and the PCM middle layer as well) under unusual circumstancesto figure out how they would behave. So I came up with this Virtual PCMTest Driver.This new Virtual PCM Test Driver has several features which can be usefulduring the userspace ALSA applications testing/fuzzing, or testing/fuzzingof the PCM middle layer. Not all of them can be implemented using theexisting virtual drivers (like dummy or loopback). Here is what can thisdriver do:- Simulate both capture and playback processes- Generate random or pattern-based capture data- Check the playback stream for containing the looped pattern- Inject delays into the playback and capturing processes- Inject errors during the PCM callbacksAlso, this driver can check the playback stream for containing thepredefined pattern, which is used in the corresponding selftest to checkthe PCM middle layer data transferring functionality. Additionally, thisdriver redefines the default RESET ioctl, and the selftest covers this PCMAPI functionality as well.The driver supports both interleaved and non-interleaved access modes, andhave separate pattern buffers for each channel. The driver supports up to4 channels and up to 8 substreams.Signed-off-by: Ivan Orlov Acked-by: Jaroslav Kysela Link: https://lore.kernel.org/r/20230606193254.20791-3-ivan.orlov0322@gmail.comSigned-off-by: Takashi Iwai List of files: /linux-6.15/tools/testing/selftests/alsa/Makefile

69218b59 - kselftest/alsa: Run PCM tests for multiple cards in parallel

Fri, 03 Feb 2023 19:52:47 +0000

kselftest/alsa: Run PCM tests for multiple cards in parallelWith each test taking 4 seconds the runtime of pcm-test can add up. Sincegenerally each card in the system is physically independent and will beunaffected by what's going on with other cards we can mitigate this bytesting each card in parallel. Make a list of cards as we enumerate thesystem and then start a thread for each, then join the threads to ensurethey have all finished. The threads each run the same tests we currentlyrun for each PCM on the card before exiting.The list of PCMs is kept global since it helps with global operationslike working out our planned number of tests and identifying missing PCMsand it seemed neater to check for PCMs on the right card in the cardthread than make every PCM loop iterate over cards as well.We don't run per-PCM tests in parallel since in embedded systems it canbe the case that resources are shared between the PCMs and operations onone PCM on a card may constrain what can be done on another PCM on the samecard leading to potentially unstable results.We use a mutex to ensure that the reporting of results is serialised and wedon't have issues with anything like the current test number, we could dothis in the kselftest framework but it seems like this might cause problemsfor other tests that are doing lower level testing and building inconstrained environments such as nolibc so this seems more sensible.Note that the ordering of the tests can't be guaranteed as things stand,this does not seem like a major problem since the numbering of tests oftenchanges as test programs are changed so results parsers are expected torely on the test name rather than the test numbers. We also now prefix themachine generated test name when printing the description of the test sincethis is logged before streaming starts.On my two card desktop system this reduces the overall runtime by athird.Signed-off-by: Mark Brown Link: https://lore.kernel.org/r/20230203-alsa-pcm-test-card-thread-v1-1-59941640ebba@kernel.orgSigned-off-by: Takashi Iwai List of files: /linux-6.15/tools/testing/selftests/alsa/Makefile

348d09fc - kselftest/alsa: pcm - move more configuration to configuration files

Tue, 27 Dec 2022 17:06:47 +0000

kselftest/alsa: pcm - move more configuration to configuration filesObtain all test parameters from the configuration files. The defaultsare defined in the pcm-test.conf file. The test count and parametersmay be variable per specific hardware.Also, handle alt_formats field now (with the fixes in the format loop).It replaces the original "automatic" logic which is not so universal.The code may be further extended to skip various tests basedon the configuration hints, if the exact PCM hardware parametersare not available for the given hardware.Signed-off-by: Jaroslav Kysela Signed-off-by: Mark Brown Link: https://lore.kernel.org/r/20221208-alsa-pcm-test-hacks-v4-2-5a152e65b1e1@kernel.orgSigned-off-by: Takashi Iwai List of files: /linux-6.15/tools/testing/selftests/alsa/Makefile

b310092e - selftests: alsa - move shared library configuration code to conf.c

Tue, 29 Nov 2022 08:53:06 +0000

selftests: alsa - move shared library configuration code to conf.cThe minimal alsa-lib configuration code is similar in both mixerand pcm tests. Move this code to the shared conf.c source file.Also, fix the build rules inspired by rseq tests. Build libatest.sowhich is linked to the both test utilities dynamically.Also, set the TEST_FILES variable for lib.mk.Cc: linux-kselftest@vger.kernel.orgCc: Shuah Khan Reported-by: Mark Brown Signed-off-by: Jaroslav Kysela Tested-by: Mark Brown Link: https://lore.kernel.org/r/20221129085306.2345763-1-perex@perex.czSigned-off-by: Takashi Iwai List of files: /linux-6.15/tools/testing/selftests/alsa/Makefile

aba51cd0 - selftests: alsa - add PCM test

Tue, 08 Nov 2022 11:59:14 +0000

selftests: alsa - add PCM testThis initial code does a simple sample transfer tests. By default,all PCM devices are detected and tested with short and longbuffering parameters for 4 seconds. If the sample transfer timingis not in a +-100ms boundary, the test fails. Only the interleavedbuffering scheme is supported in this version.The configuration may be modified with the configuration files.A specific hardware configuration is detected and activatedusing the sysfs regex matching. This allows to use the DMI string(/sys/class/dmi/id/* tree) or any other system parametersexposed in sysfs for the matching for the CI automation.The configuration file may also specify the PCM device list to detectthe missing PCM devices.v1..v2: - added missing alsa-local.h header fileCc: Mark Brown Cc: Pierre-Louis Bossart Cc: Liam Girdwood Cc: Jesse Barnes Cc: Jimmy Cheng-Yi Chiang Cc: Curtis Malainey Cc: Brian Norris Signed-off-by: Jaroslav Kysela Reviewed-by: Mark Brown Link: https://lore.kernel.org/r/20221108115914.3751090-1-perex@perex.czSigned-off-by: Takashi Iwai List of files: /linux-6.15/tools/testing/selftests/alsa/Makefile

079d93b7 - selftests: alsa: Handle pkg-config failure more gracefully

Tue, 31 May 2022 15:13:37 +0000

selftests: alsa: Handle pkg-config failure more gracefullyFollow the pattern used by other selftests like memfd and fall back on thestandard toolchain options to build with a system installed alsa-lib ifwe don't get anything from pkg-config. This reduces our build dependenciesa bit in the common case while still allowing use of pkg-config in casethere is a need for it.Signed-off-by: Mark Brown Link: https://lore.kernel.org/r/20220531151337.2933810-1-broonie@kernel.orgSigned-off-by: Takashi Iwai List of files: /linux-6.15/tools/testing/selftests/alsa/Makefile

5aaf9eff - kselftest: alsa: Add simplistic test for ALSA mixer controls kselftest

Fri, 10 Dec 2021 18:54:08 +0000

kselftest: alsa: Add simplistic test for ALSA mixer controls kselftestAdd a basic test for the mixer control interface. For every control onevery sound card in the system it checks that it can read and write thedefault value where the control supports that and for writeable controlsattempts to write all valid values, restoring the default values aftereach test to minimise disruption for users.There are quite a few areas for improvement - currently no coverage of thegeneration of notifications, several of the control types don't have anycoverage for the values and we don't have any testing of error handlingwhen we attempt to write out of range values - but this provides some basiccoverage.This is added as a kselftest since unlike other ALSA test programs it doesnot require either physical setup of the device or interactive monitoringby users and kselftest is one of the test suites that is frequently run bypeople doing general automated testing so should increase coverage. It iswritten in terms of alsa-lib since tinyalsa is not generally packaged fordistributions which makes things harder for general users interested inkselftest as a whole but it will be a barrier to people with Android.Signed-off-by: Mark Brown Reviewed-by: Shuah Khan Link: https://lore.kernel.org/r/20211210185410.740009-2-broonie@kernel.orgSigned-off-by: Takashi Iwai List of files: /linux-6.15/tools/testing/selftests/alsa/Makefile