From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>, broonie@kernel.org
Cc: alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
tiwai@suse.com, perex@perex.cz,
amadeuszx.slawinski@linux.intel.com, hdegoede@redhat.com
Subject: Re: [PATCH v2 2/5] ASoC: topology: Do not ignore route checks when parsing graphs
Date: Fri, 22 Mar 2024 20:42:44 -0500 [thread overview]
Message-ID: <2089e703-62b9-4aef-9722-488fe14d4546@linux.intel.com> (raw)
In-Reply-To: <20240308090502.2136760-3-cezary.rojewski@intel.com>
On 3/8/24 03:04, Cezary Rojewski wrote:
> One of the framework responsibilities is to ensure that the enumerated
> DPCMs are valid i.e.: a valid BE is connected to a valid FE DAI. While
> the are checks in soc-core.c and soc-pcm.c that verify this, a component
> driver may attempt to workaround this by loading an invalid graph
> through the topology file.
>
> Be strict and fail topology loading when invalid graph is encountered.
>
> Signed-off-by: Cezary Rojewski <cezary.rojewski@intel.com>
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
next prev parent reply other threads:[~2024-03-23 1:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 9:04 [PATCH v2 0/5] ASoC: Harden DAPM route checks and Intel fixes Cezary Rojewski
2024-03-08 9:04 ` [PATCH v2 1/5] ASoC: Intel: Disable route checks for Skylake boards Cezary Rojewski
2024-03-23 1:42 ` Pierre-Louis Bossart
2024-03-08 9:04 ` [PATCH v2 2/5] ASoC: topology: Do not ignore route checks when parsing graphs Cezary Rojewski
2024-03-23 1:42 ` Pierre-Louis Bossart [this message]
2024-03-08 9:05 ` [PATCH v2 3/5] ASoC: Intel: avs: ssm4567: Do not ignore route checks Cezary Rojewski
2024-03-08 9:05 ` [PATCH v2 4/5] ASoC: Intel: avs: ssm4567: Board cleanup Cezary Rojewski
2024-03-08 9:05 ` [PATCH v2 5/5] ASoC: Intel: avs: i2s_test: Remove redundant dapm routes Cezary Rojewski
2024-03-26 15:27 ` [PATCH v2 0/5] ASoC: Harden DAPM route checks and Intel fixes 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=2089e703-62b9-4aef-9722-488fe14d4546@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=hdegoede@redhat.com \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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.