Fix two MT8192 AFE probe cleanup issues that mirror the recently fixed
MT8189 and MT8196 paths.

The first patch registers a devm cleanup action for a successful
reserved-memory assignment so later probe failures and driver unbind
release it.

The second patch checks the temporary runtime resume used while
reinitializing the regmap cache and makes the regcache failure path drop
the PM reference and clear pm_runtime_bypass_reg_ctl.

Signed-off-by: Cássio Gabriel <cassiogabrielcontato@gmail.com>
---
Cássio Gabriel (2):
      ASoC: mediatek: mt8192: Release reserved memory on cleanup
      ASoC: mediatek: mt8192: Check runtime resume during probe

 sound/soc/mediatek/mt8192/mt8192-afe-pcm.c | 21 +++++++++++++++++----
 1 file changed, 17 insertions(+), 4 deletions(-)
---
base-commit: 93f1bbc69dbcbb29544769c4d6f3456749ad9013
change-id: 20260526-asoc-mt8192-probe-cleanup-3ef72f38e3d5

Best regards,
--  
Cássio Gabriel <cassiogabrielcontato@gmail.com>

On Wed, 27 May 2026 10:55:45 -0300, Cássio Gabriel wrote:
> ASoC: mediatek: mt8192 probe cleanup
> 
> Fix two MT8192 AFE probe cleanup issues that mirror the recently fixed
> MT8189 and MT8196 paths.
> 
> The first patch registers a devm cleanup action for a successful
> reserved-memory assignment so later probe failures and driver unbind
> release it.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: mediatek: mt8192: Release reserved memory on cleanup
      https://git.kernel.org/broonie/sound/c/965e17ae6751
[2/2] ASoC: mediatek: mt8192: Check runtime resume during probe
      https://git.kernel.org/broonie/sound/c/e24d5dde56a5

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