linux-kernel - Re: [PATCH V4] Docs/sound: Update codec-to-codec documentation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZyQ5OJM8k1rGog2R@archie.me>
Date: Fri, 1 Nov 2024 09:13:12 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: anish kumar <yesanishhere@...il.com>, lgirdwood@...il.com,
	broonie@...nel.org, perex@...ex.cz, tiwai@...e.com, corbet@....net
Cc: linux-kernel@...r.kernel.org, linux-sound@...r.kernel.org,
	linux-doc@...r.kernel.org
Subject: Re: [PATCH V4] Docs/sound: Update codec-to-codec documentation

On Thu, Oct 31, 2024 at 02:14:11PM -0700, anish kumar wrote:
> Updated documentation to provide more details
> for codec-to-codec connection especially around
> the scenarios and DAPM core details for C2C
> creation.
"Describe in more detail codec-to-codec connection, especially on
use cases and DAPM core details for C2C creation."
> +An ALSA-based audio system typically involves playback and capture
> +functionality, where users may require audio file playback through
> +speakers or recording from microphones. However, certain systems
> +necessitate audio data routing directly between components, such as FM
> +radio to speakers, without CPU involvement. For such scenarios, ASoC(
> +ALSA system on chip) provides a mechanism known as codec-to-codec (C2C)
"For such scenarios, ASoC (ALSA system on chip) ..."
> +connections, leveraging the Dynamic Audio Power Management (DAPM)
> +framework to facilitate direct data transfers between codecs.
> <snipped>...
> +To better understand the configuration inspired by the setup found in
> +``sound/soc/samsung/speyside.c``, here are several key points:
> +
> +1. The presence of ``c2c_params`` informs the DAPM core that the DAI link
> +   represents a C2C connection.
> +
> +2. ``c2c_params`` can be an array, and ``num_c2c_params`` defines the size
> +   of this array.
> +
> +3. If ``num_c2c_params`` is 1:
> +
> +   - The C2C DAI is configured with the provided ``snd_soc_pcm_stream``
> +     parameters.
> +
> +4. If ``num_c2c_params`` is greater than 1:
> +
> +   - A kcontrol is created, allowing the user to select the index of the
> +     ``c2c_params`` array to be used.

I guess #3 and #4 can be combined, i.e. "If ``num_c2c_params`` is 1, ...;
otherwise if ``num_c2c_params`` is greater than 1, ...".

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)