commit | 0945a70ef7b6a5cf95d2bd1892226d69c9fc9228 | [log] [tgz] |
---|---|---|
author | dvdli <dvdli@google.com> | Mon Jul 19 01:55:20 2021 +0000 |
committer | Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com> | Mon Jul 19 01:55:20 2021 +0000 |
tree | 7de2e4dd5c8e46e9a153a07a790eb4b64a19446a | |
parent | 4ed4d5684dbd41d078fbdccb99c4b2c763b39697 [diff] | |
parent | 9a41bd1c2e747d9c573b07d04a19700134e4ca53 [diff] |
[automerger skipped] fix the zero fd closing problem am: 1fa61ebcec -s ours am: 9a41bd1c2e -s ours am skip reason: Merged-In I271429b818a147917c21dece1a37e583e421c892 with SHA-1 18fff36d3f is already in history Original change: https://googleplex-android-review.googlesource.com/c/platform/external/tinyalsa_new/+/15310734 Change-Id: Ic89b521ed62c09bae045f27f6a95d877a0e68245
TinyALSA is a small library to interface with ALSA in the Linux kernel.
The aims are:
TinyALSA supports these build systems:
To build and install with Make, run the commands:
make sudo make install sudo ldconfig
TinyALSA is now available as a set of the following Debian packages from launchpad:
Package Name: | Description: |
---|---|
tinyalsa | Contains tinyplay, tinycap, tinymix and tinypcminfo |
libtinyalsa | Contains the shared library |
libtinyalsa-dev | Contains the static library and header files |
To install these packages, run the commands:
sudo apt-add-repository ppa:taylorcholberton/tinyalsa sudo apt-get update sudo apt-get install tinyalsa sudo apt-get install libtinyalsa-dev
Once installed, the man pages are available via:
man tinyplay man tinycap man tinymix man tinypcminfo man libtinyalsa-pcm man libtinyalsa-mixer
To test libtinyalsa, please follow the instructions,
Visit here to get more info to setup Bazel environment.
The test program does pcm_* operations on loopback devices. You have to insert loopback devices after your system boots up.
sudo modprobe snd-aloop sudo chmod 777 /dev/snd/*
bazel test //:tinyalsa_tests --test_output=all
The default playback device is hw:2,0 and the default capture device is hw:2,1. If your loopback devices are not hw:2,0 and hw:2,1, you can specify the loopback device.
bazel test //:tinyalsa_tests --test_output=all \ --copt=-DTEST_LOOPBACK_CARD=[loopback card] \ --copt=-DTEST_LOOPBACK_PLAYBACK_DEVICE=[loopback playback device] \ --copt=-DTEST_LOOPBACK_CAPTURE_DEVICE=[loopback capture device]
bazel coverage //:tinyalsa_tests --combined_report=lcov --test_output=all genhtml bazel-out/_coverage/_coverage_report.dat -o tinyalsa_tests_coverage