From: Jon Hunter <jonathanh@nvidia.com>
To: Guixin Liu <kanie@linux.alibaba.com>,
Thierry Reding <thierry.reding@gmail.com>,
Sowjanya Komatineni <skomatineni@nvidia.com>,
Laxman Dewangan <ldewangan@nvidia.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-tegra@vger.kernel.org, linux-spi@vger.kernel.org
Subject: Re: [PATCH] spi: tegra210-quad: downgrade the log when fall back to PIO
Date: Wed, 10 Dec 2025 04:24:19 +0000 [thread overview]
Message-ID: <e2b2288e-e8fb-484e-9675-39a0d14441fa@nvidia.com> (raw)
In-Reply-To: <20251127130207.43754-1-kanie@linux.alibaba.com>
On 27/11/2025 13:02, Guixin Liu wrote:
> When the machine boots using ACPI, Tegra cannot use DMA and falls back
> to PIO. In this case, logging these messages as "Error" may confuse
> users into thinking it is an actual error; therefore, these two log
> messages should be downgraded to "Info" level.
Which Tegra device are you using?
> Signed-off-by: Guixin Liu <kanie@linux.alibaba.com>
> ---
> drivers/spi/spi-tegra210-quad.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/spi/spi-tegra210-quad.c b/drivers/spi/spi-tegra210-quad.c
> index 3be7499db21e..2189904b931d 100644
> --- a/drivers/spi/spi-tegra210-quad.c
> +++ b/drivers/spi/spi-tegra210-quad.c
> @@ -823,8 +823,8 @@ static int tegra_qspi_init_dma(struct tegra_qspi *tqspi)
> tegra_qspi_deinit_dma(tqspi);
>
> if (err != -EPROBE_DEFER) {
> - dev_err(tqspi->dev, "cannot use DMA: %d\n", err);
> - dev_err(tqspi->dev, "falling back to PIO\n");
> + dev_info(tqspi->dev, "cannot use DMA: %d\n", err);
> + dev_info(tqspi->dev, "falling back to PIO\n");
> return 0;
> }
This change would potentially hide an actual case where the DMA
initialisation fails when booting with device-tree.
Jon
--
nvpublic
next prev parent reply other threads:[~2025-12-10 4:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 13:02 [PATCH] spi: tegra210-quad: downgrade the log when fall back to PIO Guixin Liu
2025-12-04 1:46 ` Guixin Liu
2025-12-04 12:33 ` Mark Brown
2025-12-05 2:14 ` Guixin Liu
2025-12-10 4:24 ` Jon Hunter [this message]
2025-12-11 3:44 ` Guixin Liu
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=e2b2288e-e8fb-484e-9675-39a0d14441fa@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=broonie@kernel.org \
--cc=kanie@linux.alibaba.com \
--cc=ldewangan@nvidia.com \
--cc=linux-spi@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=skomatineni@nvidia.com \
--cc=thierry.reding@gmail.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