Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     alsa-devel@alsa-project.org, Maxim Kochetkov <fido_max@inbox.ru>
Cc:     Liam Girdwood <lgirdwood@gmail.com>,
        Jaroslav Kysela <perex@perex.cz>,
        Takashi Iwai <tiwai@suse.com>,
        =?utf-8?q?Uwe_Kleine-K=C3=B6nig?= <u.kleine-koenig@pengutronix.de>,
        Charles Keepax <ckeepax@opensource.cirrus.com>,
        linux-kernel@vger.kernel.org
In-Reply-To: <20230613191552.724748-1-fido_max@inbox.ru>
References: <20230613191552.724748-1-fido_max@inbox.ru>
Subject: Re: [PATCH 1/1] ASoC: dwc: don't assign addr_width for dt configs
Message-Id: <168727110123.80037.14165724082437733133.b4-ty@kernel.org>
Date:   Tue, 20 Jun 2023 15:25:01 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Tue, 13 Jun 2023 22:15:51 +0300, Maxim Kochetkov wrote:
> For proper DMA operation addr_width must corresponds with audio format
> (S16, S24, S32, etc). Proper bus width calculations is performed by
> snd_hwparams_to_dma_slave_config(). So drop wrong addr_width asignment
> for dt configs and let snd_hwparams_to_dma_slave_config() do the job.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: dwc: don't assign addr_width for dt configs
      commit: 6f80197f40515853814d0f22e5209d53f899ab91

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