Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: anish kumar <yesanishhere@gmail.com>
Cc: lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
	tiwai@suse.com, corbet@lwn.net, linux-kernel@vger.kernel.org,
	linux-sound@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH V4] Docs/sound: Update codec-to-codec documentation
Date: Tue, 12 Nov 2024 07:54:08 +0700	[thread overview]
Message-ID: <ZzKnMLe-L7bOe9Tw@archie.me> (raw)
In-Reply-To: <CABCoZhCapQBCj=UJ78XWtzier5m34zX+bwSo4bPxEVkOdZSxRA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2325 bytes --]

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@gmail.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?

Confused...

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-11-12  0:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31 21:14 [PATCH V4] Docs/sound: Update codec-to-codec documentation anish kumar
2024-11-01  2:13 ` Bagas Sanjaya
2024-11-10 21:30   ` anish kumar
2024-11-12  0:54     ` Bagas Sanjaya [this message]
2024-11-12  1:17       ` anish kumar
2024-12-05 20:34         ` anish kumar
2024-12-06 10:34 ` Charles Keepax

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=ZzKnMLe-L7bOe9Tw@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=lgirdwood@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=yesanishhere@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox