From: Mark Brown <broonie@kernel.org>
To: Sataporn <excursively@gmail.com>
Cc: Bard Liao <yung-chuan.liao@linux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: Intel: soc-acpi-intel-ptl-match: add rt721_l3_rt1320_l3
Date: Mon, 17 Aug 2026 16:56:38 +0100 [thread overview]
Message-ID: <c75806b8-7dd1-4cac-b4ba-e457d8aacce4@sirena.org.uk> (raw)
In-Reply-To: <20260815182747.8913-1-excursively@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
On Sun, Aug 16, 2026 at 01:27:47AM +0700, Sataporn wrote:
> Add an entry describing the two amplifiers. They share aggregation
> group 1, following the existing rt712_vb_l3_rt1320_l3 entry: with
> separate groups each device asks for a DAI link named
> "SDW3-Playback-SmartAmp" and the second registration fails with
> -EEXIST.
> + {
> + .link_mask = BIT(3),
> + .links = ptl_sdw_rt721_l3_rt1320_l3,
> + .drv_name = "sof_sdw",
> + /*
> + * No monolithic topology exists for this combination; the
> + * "dummy" name marks that, so the function topologies are
> + * used and functions without one are skipped rather than
> + * failing the card.
> + */
> + .sof_tplg_filename = "sof-ptl-dummy.tplg",
> + .get_function_tplg_files = sof_sdw_get_tplg_files,
> + },
Will this match on other systems that have additional components, or
more SDCA functions active?
> {},
> };
> EXPORT_SYMBOL_GPL(snd_soc_acpi_intel_ptl_sdw_machines);
> --
> 2.43.0
>
> --
> 2.51.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-08-17 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 18:27 Sataporn
2026-08-17 4:42 ` Liao, Bard
2026-08-17 9:00 ` Sataporn Saijai
2026-08-17 15:56 ` Mark Brown [this message]
2026-08-18 3:53 ` Sataporn Saijai
2026-08-18 15:01 ` Mark Brown
2026-08-18 18:24 ` Sataporn Saijai
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=c75806b8-7dd1-4cac-b4ba-e457d8aacce4@sirena.org.uk \
--to=broonie@kernel.org \
--cc=excursively@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.dev \
--cc=yung-chuan.liao@linux.intel.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
all inboxes | Powered by JetHome®