From: Sheetal <sheetal@nvidia.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
"Mohan Kumar" <mkumard@nvidia.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
<linux-sound@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Sheetal <sheetal@nvidia.com>
Subject: [PATCH v3 00/14] ASoC: tegra: Add error logging for probe and callback failures
Date: Wed, 25 Mar 2026 10:14:23 +0000 [thread overview]
Message-ID: <20260325101437.3059693-1-sheetal@nvidia.com> (raw)
Log errors in probe and runtime error paths across Tegra audio drivers.
Use dev_err_probe() in probe paths and dev_err() in runtime callbacks.
Skip redundant logging where the underlying API already reports errors.
Changes in v3:
- Split single patch into per-driver patch series for easier review
and incremental merging.
- Drop dev_err() from tegra_ahub_put_value_enum() since the error path
is userspace-triggerable and would allow log spamming.
- Drop dev_err() from tegra210_mixer_set_audio_cif() since the driver
advertises S8 format support but this function doesn't handle it,
creating a userspace-triggerable log spam path.
Changes in v2:
- Use dev_err_probe() in all probe error paths as a defensive measure,
instead of only where -EPROBE_DEFER is currently known to be returned.
- Drop redundant error logging for devm_platform_ioremap_resource() and
devm_ioremap_resource() since these APIs already log errors internally.
Sheetal (14):
ASoC: tegra: Use dev_err_probe() in tegra186_asrc probe
ASoC: tegra: Use dev_err_probe() in tegra186_dspk probe
ASoC: tegra: Add error logging in tegra210_admaif driver
ASoC: tegra: Add error logging in tegra210_adx driver
ASoC: tegra: Use dev_err_probe() in tegra210_ahub probe
ASoC: tegra: Add error logging in tegra210_amx driver
ASoC: tegra: Use dev_err_probe() in tegra210_dmic probe
ASoC: tegra: Add error logging in tegra210_i2s driver
ASoC: tegra: Use dev_err_probe() in OPE, PEQ and MBDRC drivers
ASoC: tegra: Use dev_err_probe() in tegra210_mixer probe
ASoC: tegra: Use dev_err_probe() in tegra210_mvc probe
ASoC: tegra: Use dev_err_probe() in tegra210_sfc probe
ASoC: tegra: Use dev_err_probe() in tegra_asoc_machine probe
ASoC: tegra: Use dev_err_probe() in tegra_audio_graph_card probe
sound/soc/tegra/tegra186_asrc.c | 7 ++--
sound/soc/tegra/tegra186_dspk.c | 15 +++----
sound/soc/tegra/tegra210_admaif.c | 18 ++++----
sound/soc/tegra/tegra210_adx.c | 13 +++---
sound/soc/tegra/tegra210_ahub.c | 18 ++++----
sound/soc/tegra/tegra210_amx.c | 9 ++--
sound/soc/tegra/tegra210_dmic.c | 14 +++----
sound/soc/tegra/tegra210_i2s.c | 18 ++++----
sound/soc/tegra/tegra210_mbdrc.c | 10 ++---
sound/soc/tegra/tegra210_mixer.c | 7 ++--
sound/soc/tegra/tegra210_mvc.c | 7 ++--
sound/soc/tegra/tegra210_ope.c | 19 ++++-----
sound/soc/tegra/tegra210_peq.c | 10 ++---
sound/soc/tegra/tegra210_sfc.c | 7 ++--
sound/soc/tegra/tegra_asoc_machine.c | 70 ++++++++++++++++----------------
sound/soc/tegra/tegra_audio_graph_card.c | 21 ++++++----
16 files changed, 128 insertions(+), 135 deletions(-)
--
2.17.1
next reply other threads:[~2026-03-25 10:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 10:14 Sheetal [this message]
2026-03-25 10:14 ` [PATCH v3 01/14] ASoC: tegra: Use dev_err_probe() in tegra186_asrc probe Sheetal
2026-03-25 13:03 ` Mark Brown
2026-03-25 10:14 ` [PATCH v3 02/14] ASoC: tegra: Use dev_err_probe() in tegra186_dspk probe Sheetal
2026-03-25 10:14 ` [PATCH v3 03/14] ASoC: tegra: Add error logging in tegra210_admaif driver Sheetal
2026-03-25 13:05 ` Mark Brown
2026-03-25 10:14 ` [PATCH v3 04/14] ASoC: tegra: Add error logging in tegra210_adx driver Sheetal
2026-03-25 10:14 ` [PATCH v3 05/14] ASoC: tegra: Use dev_err_probe() in tegra210_ahub probe Sheetal
2026-03-25 13:07 ` Mark Brown
2026-03-25 10:14 ` [PATCH v3 06/14] ASoC: tegra: Add error logging in tegra210_amx driver Sheetal
2026-03-25 10:14 ` [PATCH v3 07/14] ASoC: tegra: Use dev_err_probe() in tegra210_dmic probe Sheetal
2026-03-25 13:08 ` Mark Brown
2026-03-25 10:14 ` [PATCH v3 08/14] ASoC: tegra: Add error logging in tegra210_i2s driver Sheetal
2026-03-25 10:14 ` [PATCH v3 09/14] ASoC: tegra: Use dev_err_probe() in OPE, PEQ and MBDRC drivers Sheetal
2026-03-25 13:10 ` Mark Brown
2026-03-25 10:14 ` [PATCH v3 10/14] ASoC: tegra: Use dev_err_probe() in tegra210_mixer probe Sheetal
2026-03-25 10:14 ` [PATCH v3 11/14] ASoC: tegra: Use dev_err_probe() in tegra210_mvc probe Sheetal
2026-03-25 10:14 ` [PATCH v3 12/14] ASoC: tegra: Use dev_err_probe() in tegra210_sfc probe Sheetal
2026-03-25 13:11 ` Mark Brown
2026-03-25 10:14 ` [PATCH v3 13/14] ASoC: tegra: Use dev_err_probe() in tegra_asoc_machine probe Sheetal
2026-03-25 10:14 ` [PATCH v3 14/14] ASoC: tegra: Use dev_err_probe() in tegra_audio_graph_card probe Sheetal
2026-03-25 13:18 ` (subset) [PATCH v3 00/14] ASoC: tegra: Add error logging for probe and callback failures Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260325101437.3059693-1-sheetal@nvidia.com \
--to=sheetal@nvidia.com \
--cc=broonie@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=perex@perex.cz \
--cc=thierry.reding@kernel.org \
--cc=tiwai@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox