From mboxrd@z Thu Jan 1 00:00:00 1970 From: Antonio Ospite Subject: [alsa-utils] alsaucm should come with a man page Date: Wed, 27 Jul 2016 11:48:28 +0200 Message-ID: <20160727114828.9d6c709d80084b659426e6cc@ao2.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from ao2.it (ao2.it [92.243.12.208]) by alsa0.perex.cz (Postfix) with ESMTP id 4F27E265864 for ; Wed, 27 Jul 2016 11:48:32 +0200 (CEST) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: alsa-devel-bounces@alsa-project.org To: alsa-devel@alsa-project.org Cc: Pierre-Louis Bossart , Stefan Schmidt , Justin Xu , Liam Girdwood List-Id: alsa-devel@alsa-project.org Hi, I used alsaucm to test mixer use cases for an Intel Baytrail tablet, I wanted to use bare alsa before bringing pulseaudio in, and it took some time to get my head around it. The output from the "alsaucm --help" is too terse, I had to look at the alsa-lib code[1] to see the possible IDENTIFIERs, and even then it was not clear to me that some operations, like for instance "list _devices", can only work after setting a _verb in the same _execution_, for instance this sequence doesn't work: # alsaucm -c bytcr-rt5640 set _verb HiFi # alsaucm -c bytcr-rt5640 list _devices But this command does: # alsaucm -c bytcr-rt5640 -b - <