From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Icenowy Zheng <icenowy@aosc.xyz>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Hans de Goede <hdegoede@redhat.com>, Chen-Yu Tsai <wens@csie.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mmc: sunxi: mask all Response Timeout error messages
Date: Mon, 6 Mar 2017 11:04:37 +0100 [thread overview]
Message-ID: <20170306100437.sr7mrvssdwnt7aaz@lukather> (raw)
In-Reply-To: <20170305164535.36259-1-icenowy@aosc.xyz>
[-- Attachment #1.1: Type: text/plain, Size: 1995 bytes --]
Hi,
On Mon, Mar 06, 2017 at 12:45:35AM +0800, Icenowy Zheng wrote:
> Response Timeout is very usual: it will happen when trying to run some
> commands that do not belong to the card; it will happen when some SDIO
> card transfer beyond its SDIO bandwidth; and when the MMC controller is
> set to poll the card with "broken-cd" property (the Lichee Pi series of
> boards do this), it will flood to the console and make the console
> unusable.
>
> Mask all response-timeout-only error messages, only show it when another
> error happens.
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz>
> ---
> drivers/mmc/host/sunxi-mmc.c | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mmc/host/sunxi-mmc.c b/drivers/mmc/host/sunxi-mmc.c
> index 6ffcd2838272..7828e1f57cf0 100644
> --- a/drivers/mmc/host/sunxi-mmc.c
> +++ b/drivers/mmc/host/sunxi-mmc.c
> @@ -483,10 +483,15 @@ static void sunxi_mmc_dump_errinfo(struct sunxi_mmc_host *host)
> struct mmc_command *cmd = host->mrq->cmd;
> struct mmc_data *data = host->mrq->data;
>
> - /* For some cmds timeout is normal with sd/mmc cards */
> - if ((host->int_sum & SDXC_INTERRUPT_ERROR_BIT) ==
> - SDXC_RESP_TIMEOUT && (cmd->opcode == SD_IO_SEND_OP_COND ||
> - cmd->opcode == SD_IO_RW_DIRECT))
> + /*
> + * Reading timeout is usually normal, especially when doing
> + * card-polling with "broken-cd" in device tree.
> + * If do not mask it, the RTO error message will flood the console
> + * and even hide useful error messages.
> + *
> + * Some SDIO commands will also normally timeout with non-SDIO cards.
> + */
> + if ((host->int_sum & SDXC_INTERRUPT_ERROR_BIT) == SDXC_RESP_TIMEOUT)
We really shouldn't silence legit errors.
The actual problem here is that we log them as error, we could
probably reduce it to debug.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2017-03-06 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-05 16:45 [PATCH] mmc: sunxi: mask all Response Timeout error messages Icenowy Zheng
2017-03-06 10:04 ` Maxime Ripard [this message]
2017-03-06 10:32 ` Icenowy Zheng
2017-03-06 15:53 ` Maxime Ripard
2017-03-06 17:28 ` Icenowy Zheng
2017-03-07 10:10 ` Maxime Ripard
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=20170306100437.sr7mrvssdwnt7aaz@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=hdegoede@redhat.com \
--cc=icenowy@aosc.xyz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wens@csie.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