All of lore.kernel.org
 help / color / mirror / Atom feed
From: GitHub pull_request - opened <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: src: utils: Add ccaps to query compress device capabilities
Date: Tue, 11 Aug 2026 10:58:30 +0200 (CEST)	[thread overview]
Message-ID: <18cab48a3df64600-webhooks-bot@alsa-project.org> (raw)
In-Reply-To: <alsa-project/tinycompress/pr/39@alsa-project.org>

alsa-project/tinycompress pull request #39 was opened from ujfalusi:

Add a small utility to dump the capabilities of a compress device. It uses the same device selection style as cplay (-c card, -d device) and prints the protocol version, direction, fragment size/count limits and the list of supported codecs.

For each codec the SNDRV_COMPRESS_GET_CODEC_CAPS descriptors are printed as well. Drivers not implementing the codec caps ioctl are reported instead of treated as an error.

The direction is derived from the open flags by the core, so by default the device is opened for playback first and for capture as fallback. It can be forced with -D p|c.

Example output:

  $ ccaps -c0 -d50
  Compress device hw:0,50
    protocol version:  0.4.1
    direction:         playback
    fragment size:     38400 - 131072 bytes
    fragments:         3 - 64
    codecs:            4
    [0] AAC (0x6)
    [1] MP3 (0x2)
    [2] VORBIS (0x9)
    [3] PCM (0x1)

Request URL   : https://github.com/alsa-project/tinycompress/pull/39
Patch URL     : https://github.com/alsa-project/tinycompress/pull/39.patch
Repository URL: https://github.com/alsa-project/tinycompress

           reply	other threads:[~2026-08-11  8:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <alsa-project/tinycompress/pr/39@alsa-project.org>]

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=18cab48a3df64600-webhooks-bot@alsa-project.org \
    --to=github@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /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.