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] [day] [month] [year] [list]

Message-ID: <CABCoZhC5w-uUgmsqb_m2t98NF5oftuoDTThvthoRK8m97bM+MA@mail.gmail.com>
Date: Mon, 11 Nov 2024 17:17:58 -0800
From: anish kumar <yesanishhere@...il.com>
To: Bagas Sanjaya <bagasdotme@...il.com>
Cc: lgirdwood@...il.com, broonie@...nel.org, perex@...ex.cz, tiwai@...e.com, 
	corbet@....net, 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 Mon, Nov 11, 2024 at 4:54 PM Bagas Sanjaya <bagasdotme@...il.com> wrote:
>
> On Sun, Nov 10, 2024 at 01:30:12PM -0800, anish kumar wrote:
> > On Thu, Oct 31, 2024 at 7:13 PM Bagas Sanjaya <bagasdotme@...il.com> wrote:
> > >
> > > 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."
> >
> > Sorry, I like the way it is written.
>
> What do you mean?
>
> > > > +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, ...".
> >
> > I like it this way.
>
> Sorry again but what do you mean? Keep it as-is?

Yes it is more developer friendly.
>
> Confused...
>
> --
> An old man doll... just what I always wanted! - Clara