linux-kernel - Re: [PATCH] ASoC: mediatek: mt8188: DPCM used FE and BE merged parameters

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <168978883184.125745.10740530088863632779.b4-ty@kernel.org>
Date:   Wed, 19 Jul 2023 18:47:11 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, tiwai@...e.com, perex@...ex.cz,
        matthias.bgg@...il.com, angelogioacchino.delregno@...labora.com,
        Trevor Wu <trevor.wu@...iatek.com>
Cc:     alsa-devel@...a-project.org, linux-mediatek@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: mediatek: mt8188: DPCM used FE and BE merged
 parameters

On Thu, 06 Jul 2023 14:41:23 +0800, Trevor Wu wrote:
> To ensure that DPCM takes into account the backend hardware limitations
> when user space queries the hw_params of a device, we need to add
> dpcm_merged_format, dpcm_merged_chan, and dpcm_merged_rate to the FE
> dai_links.
> 
> This patch includes only stereo FE dai_links, since multi-channel FEs
> may be reserved for specific purposes. Therefore, it may not be
> appropriate to consider BE conditions.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: mediatek: mt8188: DPCM used FE and BE merged parameters
      commit: 30019d220cf9ec4df4e5f5d9082baf5519516018

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