From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Alexandre Bailon <abailon@baylibre.com>,
chaotian.jing@mediatek.com, ulf.hansson@linaro.org,
matthias.bgg@gmail.com
Cc: linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mmc: mtk-msdc: change a log level
Date: Wed, 9 Mar 2022 10:50:50 +0100 [thread overview]
Message-ID: <affb2499-d0c8-9f8f-bfc0-3bf8b2fa431c@collabora.com> (raw)
In-Reply-To: <20220308094924.2868042-1-abailon@baylibre.com>
Il 08/03/22 10:49, Alexandre Bailon ha scritto:
> We write data to RPMB, we get many time the following log:
> mtk-msdc 11230000.mmc: phase: [map:ffffffff] [maxlen:32] [final:10]
>
> dev_info is used to print that log but it seems that log is only
> useful for debbuging. Use dev_dbg instead of dev_info.
>
> Signed-off-by: Alexandre Bailon <abailon@baylibre.com>
Hello Alexandre,
I definitely agree with this change, but the commit title is not clear enough;
can you please change it to something like
mmc: mtk-sd: Silence delay phase calculation debug log
After the change,
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> ---
> drivers/mmc/host/mtk-sd.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mmc/host/mtk-sd.c b/drivers/mmc/host/mtk-sd.c
> index d5a9c269d492..05c8b4de46f3 100644
> --- a/drivers/mmc/host/mtk-sd.c
> +++ b/drivers/mmc/host/mtk-sd.c
> @@ -1914,8 +1914,8 @@ static struct msdc_delay_phase get_best_delay(struct msdc_host *host, u32 delay)
> final_phase = (start_final + len_final / 3) % PAD_DELAY_MAX;
> else
> final_phase = (start_final + len_final / 2) % PAD_DELAY_MAX;
> - dev_info(host->dev, "phase: [map:%x] [maxlen:%d] [final:%d]\n",
> - delay, len_final, final_phase);
> + dev_dbg(host->dev, "phase: [map:%x] [maxlen:%d] [final:%d]\n",
> + delay, len_final, final_phase);
>
> delay_phase.maxlen = len_final;
> delay_phase.start = start_final;
>
prev parent reply other threads:[~2022-03-09 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 9:49 Alexandre Bailon
2022-03-09 9:50 ` AngeloGioacchino Del Regno [this message]
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=affb2499-d0c8-9f8f-bfc0-3bf8b2fa431c@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=abailon@baylibre.com \
--cc=chaotian.jing@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®