Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Cezary Rojewski <cezary.rojewski@intel.com>
To: <alsa-devel@alsa-project.org>, <broonie@kernel.org>
Cc: upstream@semihalf.com, harshapriya.n@intel.com, rad@semihalf.com,
	pierre-louis.bossart@linux.intel.com, tiwai@suse.com,
	hdegoede@redhat.com, amadeuszx.slawinski@linux.intel.com,
	cujomalainey@chromium.org, lma@semihalf.com
Subject: Re: [PATCH v2 00/14] ASoC: Intel: avs: Topology and path management
Date: Fri, 8 Apr 2022 12:54:11 +0200	[thread overview]
Message-ID: <6d7a64b4-9b5f-2fc9-e53b-603cdda6cecf@intel.com> (raw)
In-Reply-To: <20220331135246.993089-1-cezary.rojewski@intel.com>

On 2022-03-31 3:52 PM, Cezary Rojewski wrote:
> A continuation of avs-driver initial series [1]. This chapter covers
> path management and topology parsing part which was ealier path of the
> main series. The two patches that represented these two subjects in the
> initial series, have been split into many to allow for easier review and
> discussion.
> 
> AVS topology is split into two major parts: dictionaries - found within
> ASoC topology manifest - and path templates.
> 
> Dictionaries job is to reduce the total amount of memory
> occupied by topology elements. Rather than having every pipeline and
> module carry its own information, each refers to specific entry in
> specific dictionary by provided (from topology file) indexes. In
> consequence, most struct avs_tplg_xxx are made out of pointers.
> 
> Path templates are similar to path descriptions found in skylake-driver
> and they describe how given path shall look like in runtime - number of
> modules and pipelines that shape it and how they are laid out. A single
> path template is tied either to FE or BE and thus at most to a single,
> user-visible endpoint when speaking of FE.
> 
> Path is a software representation of its ADSP firmware equivalent. It's
> a logical container for pipelines which are themselves containers - this
> time for modules i.e. processing units.
> Depending on the number of audio formats supported, each path template
> may carry one or more descriptions of given path. During runtime, when
> audio format is known, description matching said format is selected and
> used when instantiating path on ADSP firmware side through IPCs.
> 
> 
> Changes v1 -> v2:
> - fixed 'set but not used' warning in patch 10/14 as mentioned by ikp
>    builder
> 
> 
> Changes RFC -> v1:
> - Plenty of rewordings and spelling fixes as requested by Pierre
> - any sysfs-functionality-related left in RFC dropped, will be part of
>    separate subject in the future
> - separated parsing of formatted strings into: "Support link_mask
>    formatted string" patch, increasing series size to 14 patches
> 
> 
> [1]: https://lore.kernel.org/alsa-devel/20220207122108.3780926-1-cezary.rojewski@intel.com/T/#t


Should I resend this one? Would like to move forward with the follow up 
series so the skylake-driver can be finally replaced :)


Regards,
Czarek

  parent reply	other threads:[~2022-04-08 10:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 13:52 [PATCH v2 00/14] ASoC: Intel: avs: Topology and path management Cezary Rojewski
2022-03-31 13:52 ` [PATCH v2 01/14] ASoC: Intel: avs: Declare vendor tokens Cezary Rojewski
2022-03-31 13:52 ` [PATCH v2 02/14] ASoC: Intel: avs: Add topology parsing infrastructure Cezary Rojewski
2022-06-09 19:57   ` Pierre-Louis Bossart
2022-06-10 10:01     ` Cezary Rojewski
2022-03-31 13:52 ` [PATCH v2 03/14] ASoC: Intel: avs: Parse module-extension tuples Cezary Rojewski
2022-03-31 13:52 ` [PATCH v2 04/14] ASoC: Intel: avs: Parse pplcfg and binding tuples Cezary Rojewski
2022-03-31 13:52 ` [PATCH v2 05/14] ASoC: Intel: avs: Parse pipeline and module tuples Cezary Rojewski
2022-03-31 13:52 ` [PATCH v2 06/14] ASoC: Intel: avs: Parse path and path templates tuples Cezary Rojewski
2022-03-31 13:52 ` [PATCH v2 07/14] ASoC: Intel: avs: Add topology loading operations Cezary Rojewski
2022-03-31 13:52 ` [PATCH v2 08/14] ASoC: Intel: avs: Support link_mask formatted string Cezary Rojewski
2022-03-31 13:52 ` [PATCH v2 09/14] ASoC: Intel: avs: Declare path and its components Cezary Rojewski
2022-03-31 13:52 ` [PATCH v2 10/14] ASoC: Intel: avs: Path creation and freeing Cezary Rojewski
2022-03-31 13:52 ` [PATCH v2 11/14] ASoC: Intel: avs: Path state management Cezary Rojewski
2022-03-31 13:52 ` [PATCH v2 12/14] ASoC: Intel: avs: Arm paths after creating them Cezary Rojewski
2022-03-31 13:52 ` [PATCH v2 13/14] ASoC: Intel: avs: Prepare modules before bindings them Cezary Rojewski
2022-03-31 13:52 ` [PATCH v2 14/14] ASoC: Intel: avs: Configure modules according to their type Cezary Rojewski
2022-04-08 10:54 ` Cezary Rojewski [this message]
2022-04-08 11:16   ` [PATCH v2 00/14] ASoC: Intel: avs: Topology and path management Mark Brown
2022-04-20 21:40 ` 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=6d7a64b4-9b5f-2fc9-e53b-603cdda6cecf@intel.com \
    --to=cezary.rojewski@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=cujomalainey@chromium.org \
    --cc=harshapriya.n@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=lma@semihalf.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=rad@semihalf.com \
    --cc=tiwai@suse.com \
    --cc=upstream@semihalf.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