Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) client-ip=23.128.96.37;
From:   Mark Brown <broonie@kernel.org>
To:     Richard Fitzgerald <rf@opensource.cirrus.com>
Cc:     linux-kernel@vger.kernel.org, patches@opensource.cirrus.com,
        alsa-devel@alsa-project.org
In-Reply-To: <20231009153412.30380-1-rf@opensource.cirrus.com>
References: <20231009153412.30380-1-rf@opensource.cirrus.com>
Subject: Re: [PATCH] ASoC: cs35l56: ASP1 DOUT must default to Hi-Z when not
 transmitting
Message-Id: <169696281081.221758.5630336947565213531.b4-ty@kernel.org>
Date:   Tue, 10 Oct 2023 19:33:30 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Mon, 09 Oct 2023 16:34:12 +0100, Richard Fitzgerald wrote:
> The ASP1 DOUT line must be defaulted to be high-impedance when
> it is not actually transmitting data for an active channel.
> 
> In non-SoundWire modes ASP1 will usually be shared by multiple
> amps so each amp must only drive the line during the slot for
> an enabled TX channel.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: cs35l56: ASP1 DOUT must default to Hi-Z when not transmitting
      commit: 1bba0badff0ede8dc51641cff4b153422baa3369

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark