From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] mmc: bcm2835: print some informational messages during reset
Date: Wed, 14 Feb 2018 08:50:16 -0800 [thread overview]
Message-ID: <FAD84DC4-510C-4AED-A310-A8F6D6FB4B5D@gmail.com> (raw)
In-Reply-To: <57ff1e429a7fc12300a3cca0c5e9a637beed0d3a.1518619058.git.msuchanek@suse.de>
On February 14, 2018 6:38:58 AM PST, Michal Suchanek <msuchanek@suse.de> wrote:
>The previous patch does reset during hardware error so make the reset
>progress more visible.
Based on your previous email it looks like this can happen quite frequently so we might be spamming the kernel log with such reset messages. Turning this into a debug print would not be great either, how about a custom sysfs attribute counting the number of times a reset was done?
We should ideally root cause this but I am sure we can.
--
Florian
next prev parent reply other threads:[~2018-02-14 16:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 14:38 [PATCH 1/2] mmc: bcm2835: reset host on timeout Michal Suchanek
2018-02-14 14:38 ` [PATCH 2/2] mmc: bcm2835: print some informational messages during reset Michal Suchanek
2018-02-14 16:50 ` Florian Fainelli [this message]
2018-02-14 16:50 ` Florian Fainelli
2018-02-14 19:47 ` Michal Suchánek
2018-02-15 18:22 ` Stefan Wahren
2018-03-04 15:46 ` Michal Suchánek
2018-02-14 14:58 ` [PATCH 1/2] mmc: bcm2835: reset host on timeout Stefan Wahren
2018-02-14 15:36 ` Michal Suchánek
2018-02-14 16:13 ` Michal Suchánek
2018-02-14 16:49 ` Stefan Wahren
2018-02-14 19:24 ` Michal Suchánek
2018-02-14 20:30 ` Stefan Wahren
2018-03-04 15:57 ` Michal Suchánek
2018-03-04 18:11 ` Stefan Wahren
2018-03-04 18:44 ` Michal Suchánek
2018-03-03 13:58 ` Stefan Wahren
2018-03-04 16:04 ` Michal Suchánek
2018-03-04 16:36 ` Michal Suchánek
2018-03-04 18:15 ` Stefan Wahren
2018-03-06 19:21 ` Michal Suchánek
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=FAD84DC4-510C-4AED-A310-A8F6D6FB4B5D@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).