From: Thierry Reding <thierry.reding@gmail.com>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>,
Krishna Yarlagadda <kyarlagadda@nvidia.com>,
linux-serial@vger.kernel.org, linux-tegra@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] serial: tegra: Only print FIFO error message when an error occurs
Date: Wed, 30 Jun 2021 14:11:20 +0200 [thread overview]
Message-ID: <YNxfaEDFIW7d7rYi@orome.fritz.box> (raw)
In-Reply-To: <20210630094601.136280-1-jonathanh@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1772 bytes --]
On Wed, Jun 30, 2021 at 10:46:01AM +0100, Jon Hunter wrote:
> The Tegra serial driver always prints an error message when enabling the
> FIFO for devices that have support for checking the FIFO enable status.
> Fix this by only display the error message, when an error occurs.
>
> Fixes: 222dcdff3405 ("serial: tegra: check for FIFO mode enabled status")
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> drivers/tty/serial/serial-tegra.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/tty/serial/serial-tegra.c b/drivers/tty/serial/serial-tegra.c
> index 222032792d6c..cd481f7ba8eb 100644
> --- a/drivers/tty/serial/serial-tegra.c
> +++ b/drivers/tty/serial/serial-tegra.c
> @@ -1045,9 +1045,10 @@ static int tegra_uart_hw_init(struct tegra_uart_port *tup)
>
> if (tup->cdata->fifo_mode_enable_status) {
> ret = tegra_uart_wait_fifo_mode_enabled(tup);
> - dev_err(tup->uport.dev, "FIFO mode not enabled\n");
> - if (ret < 0)
> + if (ret < 0) {
> + dev_err(tup->uport.dev, "FIFO mode not enabled\n");
The error message seems a bit confusing. I read this as meaning "FIFO
mode was expected to be enabled but wasn't" whereas this really seems to
mean that for some reason the FIFO enable timed out.
In the former case it sounds like a some configuration mismatch, while
it's really something that went wrong during the process of enabling the
FIFO mode.
So I wonder if this should perhaps be something like:
dev_err(tup->uport.dev, "FIFO mode enable timed out\n");
or something along those lines.
That said, this is a pre-existing problem and it's a bit pedantic, so in
either case:
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-06-30 12:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 9:46 [PATCH] serial: tegra: Only print FIFO error message when an error occurs Jon Hunter
2021-06-30 12:11 ` Thierry Reding [this message]
2021-06-30 12:49 ` Jon Hunter
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=YNxfaEDFIW7d7rYi@orome.fritz.box \
--to=thierry.reding@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kyarlagadda@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-serial@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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