mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
	broonie@kernel.org
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@opensource.cirrus.com
Subject: Re: [PATCH 0/2] ASoC: cs35l56/57/62/63: Use the correct SoundWire DP for feedback
Date: Tue, 6 Oct 2026 10:53:41 +0100	[thread overview]
Message-ID: <d510a866-86c8-467a-8831-b373636874bf@opensource.cirrus.com> (raw)
In-Reply-To: <32e25f8c-9c96-4385-9f5f-a7cf8b11ef57@linux.dev>

On 05/10/2026 7:33 pm, Pierre-Louis Bossart wrote:
> On 10/5/26 17:52, Richard Fitzgerald wrote:
>> The amp feedback path (AEC) was incorrectly using SoundWire DP3.
>> The firmware outputs SDCA OT25 feedback on DP4. DP3 is reserved for
>> SDCA companion amp.
>>
>> This series adds a DAI for OT25 and switches the sdw machine driver
>> to use the new DAI for the feedback path.
> 
> Is there any merit in keeping this DP3 exposed as a capture DAI, if
> indeed it's intended to be a side connection for a companion chip?

I kept this patch to a minimum because it is a Fixes: so it must apply
to older kernels.

However, you are correct. DP3 isn't used now. Not even on companion amp. 
DP3 is a companion output from the amp (SDCA OT127), but Cirrus
companion amp goes codec->amp so uses DP1 on the amp.

When the driver was being written the SDCA spec and firmware behavior
were not fully defined so pairing of the symmetrical DP1+DP3
(for play+capture) was carried forward from previous amps. But SDCA
doesn't provide any sort of UCM capability - widgets on the device have
defined, fixed functionality that has to be preconfigured by the
firmware to match what SDCA needs. Ultimately DP4 was more suitable for
OT25. DP4 also works for loopback testing.

Removing DP3 would also solve some other problems that the driver and
firmware are both "owning" the registers. We originally attempted to
sync this up, then gave up on that complexity and overwrite the register
settings the firmware made.


      reply	other threads:[~2026-10-06  9:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 15:52 Richard Fitzgerald
2026-10-05 15:52 ` [PATCH 1/2] ASoC: cs35l56: Add DAI for SDCA OT25 stream Richard Fitzgerald
2026-10-05 15:52 ` [PATCH 2/2] ASoC: sdw_utils: Switch CS35L56/57/62/63 to use OT25 DAI Richard Fitzgerald
2026-10-05 18:33 ` [PATCH 0/2] ASoC: cs35l56/57/62/63: Use the correct SoundWire DP for feedback Pierre-Louis Bossart
2026-10-06  9:53   ` Richard Fitzgerald [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=d510a866-86c8-467a-8831-b373636874bf@opensource.cirrus.com \
    --to=rf@opensource.cirrus.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=pierre-louis.bossart@linux.dev \
    /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®