public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Richard Fitzgerald <rf@opensource.cirrus.com>,
	broonie@kernel.org, cezary.rojewski@intel.com,
	peter.ujfalusi@linux.intel.com, yung-chuan.liao@linux.intel.com,
	kai.vehmanen@linux.intel.com
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	patches@opensource.cirrus.com
Subject: Re: [PATCH 10/10] ASoC: Intel: soc-acpi: Add CS35L56 Soundwire to TGL
Date: Wed, 22 Feb 2023 09:31:52 -0500	[thread overview]
Message-ID: <5d92a38b-6a5c-8960-1e20-5793a0bb5da4@linux.intel.com> (raw)
In-Reply-To: <941c3c3f-673f-a4b8-092d-d495de9da9dd@opensource.cirrus.com>



On 2/22/23 06:48, Richard Fitzgerald wrote:
> On 21/02/2023 16:52, Pierre-Louis Bossart wrote:
>>
>>> +static const struct snd_soc_acpi_link_adr
>>> up_extreme_cs35l56_sdw0_one[] = {
>>> +    {
>>> +        .mask = BIT(0),
>>> +        .num_adr = 1,
>>> +        .adr_d = cs35l56_sdw0_adr,
>>> +    },
>>> +    {}
>>> +};
>>> +
>>> +static const struct snd_soc_acpi_link_adr
>>> up_extreme_cs35l56_sdw0_four[] = {
>>> +    {
>>> +        .mask = BIT(0),
>>> +        .num_adr = 4,
>>> +        .adr_d = cs35l56_sdw0_adr,
>>> +    },
>>> +    {}
>>> +};
>>
>> If the machine driver has support for the 2-amplifier configuration,
>> shouldn't it be present here as well?
>>
> 
> Not necessarily.
> It's not a setup we're currently using on this initial TGL
> configuration.
> 
> The machine driver we'd expect to work on multiple hardware. The
> counting algorithm has to go through "2" anyway, and the code to
> handle that is so trivial we may as well include it.

it's fine. usually we are more conservative and have a 1:1 match between
the soc-acpi tables and machine driver, but it doesn't hurt to add the
2-amp case in the machine driver.

      reply	other threads:[~2023-02-22 14:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 16:14 [PATCH 00/10] ASoC: Initial support for Cirrus Logic CS35L56 Richard Fitzgerald
2023-02-17 16:14 ` [PATCH 01/10] firmware: cs_dsp: Introduce no_core_startstop for self-booting DSPs Richard Fitzgerald
2023-02-17 16:14 ` [PATCH 02/10] ASoC: wm_adsp: Use no_core_startstop to prevent creating preload control Richard Fitzgerald
2023-02-17 16:14 ` [PATCH 03/10] firmware: cs_dsp: Support DSPs that don't require firmware download Richard Fitzgerald
2023-02-17 16:14 ` [PATCH 04/10] ASoC: wm_adsp: " Richard Fitzgerald
2023-02-17 16:14 ` [PATCH 05/10] ASoC: wm_adsp: Expose the DSP boot work actions as wm_adsp_power_up() Richard Fitzgerald
2023-02-17 16:14 ` [PATCH 06/10] ASoC: wm_adsp: Add support for loading bin files without wmfw Richard Fitzgerald
2023-02-17 16:14 ` [PATCH 07/10] ASoC: wm_adsp: Simplify the logging of requested firmware files Richard Fitzgerald
2023-02-17 16:14 ` [PATCH 08/10] ASoC: cs35l56: Add driver for Cirrus Logic CS35L56 Richard Fitzgerald
2023-02-21 16:45   ` Pierre-Louis Bossart
2023-02-21 17:18     ` Richard Fitzgerald
2023-02-21 17:58       ` Pierre-Louis Bossart
2023-02-22 11:16         ` Richard Fitzgerald
2023-02-17 16:14 ` [PATCH 09/10] ASoC: Intel: sof_sdw: Add support " Richard Fitzgerald
2023-02-21 16:49   ` Pierre-Louis Bossart
2023-02-21 17:32     ` Richard Fitzgerald
2023-02-21 18:03       ` Pierre-Louis Bossart
2023-02-22 11:39         ` Richard Fitzgerald
2023-02-17 16:14 ` [PATCH 10/10] ASoC: Intel: soc-acpi: Add CS35L56 Soundwire to TGL Richard Fitzgerald
2023-02-21 16:52   ` Pierre-Louis Bossart
2023-02-22 11:48     ` Richard Fitzgerald
2023-02-22 14:31       ` Pierre-Louis Bossart [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=5d92a38b-6a5c-8960-1e20-5793a0bb5da4@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=rf@opensource.cirrus.com \
    --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