From: bui duc phuc <phucduc.bui@gmail.com>

Hi all,

This series contains a few small cleanups for the Tegra ASoC drivers.
 - Use dev_err_probe() for regmap initialization failures.
 - Return the original error from snd_soc_add_component_controls().
 - Use devm_clk_get_optional() for the optional sync_input clock.

Overall, this simplifies the error paths and makes the code more
consistent.

Best regards,
Phuc

bui duc phuc (4):
  ASoC: tegra: tegra20_das: Use dev_err_probe() for error handling
  ASoC: tegra: tegra210_adx: Return the original error directly
  ASoC: tegra: tegra210_amx: Return the original error directly
  ASoC: tegra: tegra210: Use devm_clk_get_optional() for sync_input
    clock

 sound/soc/tegra/tegra20_das.c  |  7 +++----
 sound/soc/tegra/tegra210_adx.c | 12 ++++--------
 sound/soc/tegra/tegra210_amx.c | 12 ++++--------
 sound/soc/tegra/tegra210_i2s.c | 10 +++++-----
 4 files changed, 16 insertions(+), 25 deletions(-)

-- 
2.43.0

On Wed, 15 Jul 2026 12:11:11 +0700, phucduc.bui@gmail.com wrote:
> ASoC: tegra: Simplify error handling
> 
> From: bui duc phuc <phucduc.bui@gmail.com>
> 
> Hi all,
> 
> This series contains a few small cleanups for the Tegra ASoC drivers.
>  - Use dev_err_probe() for regmap initialization failures.
>  - Return the original error from snd_soc_add_component_controls().
>  - Use devm_clk_get_optional() for the optional sync_input clock.
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: tegra: tegra20_das: Use dev_err_probe() for error handling
      https://git.kernel.org/broonie/sound/c/70d0d7b24d86
[2/4] ASoC: tegra: tegra210_adx: Return the original error directly
      https://git.kernel.org/broonie/sound/c/b82384bffb27
[3/4] ASoC: tegra: tegra210_amx: Return the original error directly
      https://git.kernel.org/broonie/sound/c/f7cbc51424cd
[4/4] ASoC: tegra: tegra210: Use devm_clk_get_optional() for sync_input clock
      https://git.kernel.org/broonie/sound/c/226791fa6dbb

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