From: Mark Brown <broonie@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: tiwai@suse.de, linux-sound@vger.kernel.org, bard.liao@intel.com,
peter.ujfalusi@linux.intel.com
Subject: Re: [PATCH v2 0/7] ALSA/ASoC: Intel: add I2S function topology support
Date: Wed, 23 Sep 2026 10:41:41 +0200 [thread overview]
Message-ID: <arOQxUNzv7CXiPDc@sirena.co.uk> (raw)
In-Reply-To: <20260923052832.2392758-1-yung-chuan.liao@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 441 bytes --]
On Wed, Sep 23, 2026 at 01:28:25PM +0800, Bard Liao wrote:
> Currently, function topology is only used by the SoundWire machines.
> Extend the support to the I2S machines.
>
> The only ALSA change is to lower the log level. Let's go through the
> ASoC tree.
>
> v2: change sscanf(dai_link->name, "SSP%d", &ssp_port) to %u as ssp_port
> is unsigned int.
As I mentioned yesterday please send an incremental change for this.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-09-23 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 5:28 [PATCH v2 0/7] ALSA/ASoC: Intel: add I2S function topology support Bard Liao
2026-09-23 5:28 ` [PATCH v2 1/7] ASoC: SOF: get nhlt from all topologies Bard Liao
2026-09-23 5:28 ` [PATCH v2 2/7] ALSA: intel-nhlt: lower intel_nhlt_ssp_device_type log level Bard Liao
2026-09-23 5:28 ` [PATCH v2 3/7] ASoC: Intel: sof-function-topology-lib: create common helpers Bard Liao
2026-09-23 5:28 ` [PATCH v2 4/7] ASoC: Intel: sof-function-topology-lib: skip non-exist file in best_effort mode Bard Liao
2026-09-23 5:28 ` [PATCH v2 5/7] ASoC: Intel: sof-function-topology-lib: add I2S support for sof_sdw_get_tplg_files Bard Liao
2026-09-23 5:28 ` [PATCH v2 6/7] ASoC: Intel: sof-function-topology-lib: add get_function_topology for I2S machines Bard Liao
2026-09-23 5:28 ` [PATCH v2 7/7] ASoC: soc-acpi-intel-ptl-match: I2S machines: use function topology Bard Liao
2026-09-23 8:41 ` Mark Brown [this message]
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=arOQxUNzv7CXiPDc@sirena.co.uk \
--to=broonie@kernel.org \
--cc=bard.liao@intel.com \
--cc=linux-sound@vger.kernel.org \
--cc=peter.ujfalusi@linux.intel.com \
--cc=tiwai@suse.de \
--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