From: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-sound@vger.kernel.org, Cezary Rojewski <cezary.rojewski@intel.com>
Subject: Re: [PATCH v2] ASoC: soc-core: add snd_soc_dapm_add_routes_with_card()
Date: Wed, 8 Jan 2025 09:44:21 +0100 [thread overview]
Message-ID: <c0c0d0a7-4272-4e2f-b128-b72b9f9f8f8e@linux.intel.com> (raw)
In-Reply-To: <87ldvmknrz.wl-kuninori.morimoto.gx@renesas.com>
On 1/8/2025 4:06 AM, Kuninori Morimoto wrote:
> Some device want to ignore snd_soc_dapm_add_routes() error, thus
> card->disable_route_checks flags had been added for such purpose. Because
> of this, ASoC has duplicate code for it. Let's adds new
> snd_soc_dapm_add_routes_with_card(), and share the error message handling.
>
> We don't need to indicate error message on this function, because it will
> be indicated from snd_soc_dapm_add_route().
>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
card->disable_route_checks is a leftover from skylake driver which had
partial routes in some topologies, as skylake driver was removed,
perhaps we can remove the field altogether?
Quick grep shows that there is only one board left which sets it:
sound/soc/intel/boards/skl_hda_dsp_generic.c:
card->disable_route_checks = true;
and it only does it after checking that parent driver isn't SOF, and as
skylake driver was removed it is dead code (it was shared between SOF
and skylake drivers).
As such I would recommend removing whole thing altogether ;)
next prev parent reply other threads:[~2025-01-08 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 3:06 [PATCH v2] ASoC: soc-core: add snd_soc_dapm_add_routes_with_card() Kuninori Morimoto
2025-01-08 8:44 ` Amadeusz Sławiński [this message]
2025-01-08 23:38 ` Kuninori Morimoto
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=c0c0d0a7-4272-4e2f-b128-b72b9f9f8f8e@linux.intel.com \
--to=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-sound@vger.kernel.org \
/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