All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Antonio Ospite <ao2@ao2.it>
Cc: alsa-devel@alsa-project.org,
	Stefan Schmidt <stefan@slimlogic.co.uk>,
	Liam Girdwood <lrg@slimlogic.co.uk>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Justin Xu <justinx@slimlogic.co.uk>
Subject: Re: [alsa-utils] alsaucm should come with a man page
Date: Wed, 03 Aug 2016 17:57:49 +0200	[thread overview]
Message-ID: <s5hmvkt975u.wl-tiwai@suse.de> (raw)
In-Reply-To: <20160727114828.9d6c709d80084b659426e6cc@ao2.it>

On Wed, 27 Jul 2016 11:48:28 +0200,
Antonio Ospite wrote:
> 
> 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 - <<EOM
> set _verb HiFi
> list _devces
> EOM
> 
> Now that I know something more it makes sense: UCM just operates on
> mixer settings, it does not have its own external state.
> 
> However, my point is that a man page explaining these things can make
> the life easier to new users.
> 
> It would be better if alsa/UCM developers wrote the man page, but if no
> one steps up I guess I could draft a first version myself.

Go ahead, please post your draft version.  That's already helpful.


thanks,

Takashi

  reply	other threads:[~2016-08-03 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27  9:48 [alsa-utils] alsaucm should come with a man page Antonio Ospite
2016-08-03 15:57 ` Takashi Iwai [this message]
2016-08-08 16:30   ` Antonio Ospite
2016-09-23 16:37     ` Antonio Ospite
2016-09-29  8:00       ` Takashi Iwai
2016-10-26 17:01         ` Antonio Ospite
2016-12-02 12:11           ` Antonio Ospite
2016-12-02 12:59             ` Liam Girdwood
2016-12-02 13:23               ` Takashi Iwai
2016-12-02 13:47                 ` Antonio Ospite

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5hmvkt975u.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=ao2@ao2.it \
    --cc=justinx@slimlogic.co.uk \
    --cc=lrg@slimlogic.co.uk \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=stefan@slimlogic.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.