[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <30f022a5-7ab1-4b2d-b4c1-5a209ec67c5b@linux.intel.com>
Date: Tue, 23 Jan 2024 09:34:00 +0100
From: Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
To: Maciej Strozek <mstrozek@...nsource.cirrus.com>,
Mark Brown <broonie@...nel.org>
Cc: Cezary Rojewski <cezary.rojewski@...el.com>,
Liam Girdwood <lgirdwood@...il.com>,
Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
Kai Vehmanen <kai.vehmanen@...ux.intel.com>, alsa-devel@...a-project.org,
patches@...nsource.cirrus.com, linux-sound@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] ASoC: Intel: mtl-match: Add cs42l43_l0 cs35l56_l23 for
MTL
On 1/22/24 16:15, Maciej Strozek wrote:
It wouldn't hurt to add a brief commit message describing what the
hardware layout is, specifically how the mics are handled.
It's also best to submit the corresponding machine driver updates at the
same time to check for consistency.
> },
> + {
> + .link_mask = BIT(0) | BIT(2) | BIT(3),
> + .links = cs42l43_link0_cs35l56_link2_link3,
> + .drv_name = "sof_sdw",
> + .sof_tplg_filename = "sof-mtl-cs42l43-l0-cs35l56-l23.tplg",
was this topology submitted to the SOF tree? I don't see it, usually we
review topology/acpi/machine stuff together to avoid disconnects.
> + },
> {
> .link_mask = GENMASK(2, 0),
> .links = mtl_cs42l43_cs35l56,
> --
> 2.34.1
>
Powered by blists - more mailing lists