From: Bagas Sanjaya <bagasdotme@gmail.com>
To: anish kumar <yesanishhere@gmail.com>,
lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, corbet@lwn.net
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-sound@vger.kernel.org
Subject: Re: [PATCH V3] ALSA: machine: update documentation
Date: Mon, 11 Nov 2024 17:56:16 +0700 [thread overview]
Message-ID: <ZzHi0BaxIEStMsY2@archie.me> (raw)
In-Reply-To: <20241109192231.11623-1-yesanishhere@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2222 bytes --]
On Sat, Nov 09, 2024 at 11:22:31AM -0800, anish kumar wrote:
> diff --git a/Documentation/sound/soc/machine.rst b/Documentation/sound/soc/machine.rst
> index 515c9444deaf..9db132bc0070 100644
> --- a/Documentation/sound/soc/machine.rst
> +++ b/Documentation/sound/soc/machine.rst
> @@ -71,6 +71,18 @@ struct snd_soc_dai_link is used to set up each DAI in your machine. e.g.
> .ops = &corgi_ops,
> };
>
> +In the above struct, dai’s are registered using names but you can pass
> +either dai name or device tree node but not both. Also, names used here
> +for cpu/codec/platform dais should be globally unique.
> +
> +Additionaly below example macro can be used to register cpu, codec and
> +platform dai::
> +
> + SND_SOC_DAILINK_DEFS(wm2200_cpu_dsp,
> + DAILINK_COMP_ARRAY(COMP_CPU("samsung-i2s.0")),
> + DAILINK_COMP_ARRAY(COMP_CODEC("spi0.0", "wm0010-sdi1")),
> + DAILINK_COMP_ARRAY(COMP_PLATFORM("samsung-i2s.0")));
> +
> struct snd_soc_card then sets up the machine with its DAIs. e.g.
> ::
>
> @@ -81,6 +93,10 @@ struct snd_soc_card then sets up the machine with its DAIs. e.g.
> .num_links = 1,
> };
>
> +Following this, ``devm_snd_soc_register_card`` can be used to register
> +the sound card. During the registration, the individual components
> +such as the codec, CPU, and platform are probed. If all these components
> +are successfully probed, the sound card gets registered.
>
> Machine Power Map
> -----------------
> @@ -95,3 +111,13 @@ Machine Controls
> ----------------
>
> Machine specific audio mixer controls can be added in the DAI init function.
> +
> +
> +Clocking Controls
> +-----------------
> +
> +As previously noted, clock configuration is handled within the machine driver.
> +For details on the clock APIs that the machine driver can utilize for
> +setup, please refer to Documentation/sound/soc/clocking.rst. However, the
> +callback needs to be registered by the CPU/Codec/Platform drivers to configure
> +the clocks that is needed for the corresponding device operation.
Looks good, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-11-11 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 19:22 [PATCH V3] ALSA: machine: update documentation anish kumar
2024-11-11 10:56 ` Bagas Sanjaya [this message]
2024-11-11 14:21 ` Mark Brown
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=ZzHi0BaxIEStMsY2@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 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.