Linux MultiMedia Card development
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: Peter Geis <pgwipeout@gmail.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Heiko Stuebner <heiko@sntech.de>,
	linux-mmc@vger.kernel.org,
	arm-mail-list <linux-arm-kernel@lists.infradead.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mmc: host: dw-mmc-rockchip: avoid logspam when cd-broken
Date: Tue, 1 Mar 2022 12:38:17 +0000	[thread overview]
Message-ID: <54b24f3d-3762-abbd-5ac4-dc5728f2fe4e@arm.com> (raw)
In-Reply-To: <CAMdYzYq0A4FitRGe49fxvjbwLUCi_KGwCtfz7pmayt_dK=r32w@mail.gmail.com>

On 2022-03-01 11:49, Peter Geis wrote:
> On Tue, Mar 1, 2022 at 6:23 AM Robin Murphy <robin.murphy@arm.com> wrote:
>>
>> On 2022-02-28 22:36, Peter Geis wrote:
>>> The dw_mmc-rockchip driver drops a large amound of logspam constantly
>>> when the cd-broken flag is enabled.
>>> Set the warning to be debug ratelimited in this case.
>>
>> Isn't this just papering over some fundamental problem with the clock?
>> If it's failing to set the expected rate for communicating with a card,
>> then presumably that's an issue for correct operation in general? The
>> fact that polling for a card makes a lot more of that communication
>> happen seems unrelated :/
> 
> Good Morning,
> 
> This only happens when a card is not inserted, so communication cannot happen.

Well, I suppose there's a philosophical question in there about whether 
shouting into the void counts as "communication", but AFAIR what the 
polling function does is power up the controller, send a command, and 
see if it gets a response.

If the clock can't be set to the proper rate for low-speed discovery, 
some or all cards may not be detected properly. Conversely if it is 
already at a slow enough rate for discovery but can't be set higher once 
a proper communication mode has been established, data transfer 
performance will be terrible. Either way, it is not OK in general for 
clk_set_rate() to fail, hence the warning. You have a clock driver problem.

Cheers,
Robin.

> I found it while lighting off the SoQuartz module.
> As it is pin compatible with the RPi CM4, and the CM4 does not have a
> card detect line, sdmmc is non functional without cd-broken.
> This led to the fun spew when there wasn't a card inserted as this
> function is called every poll tick.
> 
> Thanks,
> Peter
> 
>>
>> Robin.
>>
>>> Signed-off-by: Peter Geis <pgwipeout@gmail.com>
>>> ---
>>>    drivers/mmc/host/dw_mmc-rockchip.c | 9 +++++++--
>>>    1 file changed, 7 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/mmc/host/dw_mmc-rockchip.c b/drivers/mmc/host/dw_mmc-rockchip.c
>>> index 95d0ec0f5f3a..d0ebf0afa42a 100644
>>> --- a/drivers/mmc/host/dw_mmc-rockchip.c
>>> +++ b/drivers/mmc/host/dw_mmc-rockchip.c
>>> @@ -50,8 +50,13 @@ static void dw_mci_rk3288_set_ios(struct dw_mci *host, struct mmc_ios *ios)
>>>                cclkin = ios->clock * RK3288_CLKGEN_DIV;
>>>
>>>        ret = clk_set_rate(host->ciu_clk, cclkin);
>>> -     if (ret)
>>> -             dev_warn(host->dev, "failed to set rate %uHz\n", ios->clock);
>>> +     if (ret) {
>>> +             /* this screams when card detection is broken */
>>> +             if (host->slot->mmc->caps & MMC_CAP_NEEDS_POLL)
>>> +                     dev_dbg_ratelimited(host->dev, "failed to set rate %uHz\n", ios->clock);
>>> +             else
>>> +                     dev_warn(host->dev, "failed to set rate %uHz\n", ios->clock);
>>> +     }
>>>
>>>        bus_hz = clk_get_rate(host->ciu_clk) / RK3288_CLKGEN_DIV;
>>>        if (bus_hz != host->bus_hz) {

  reply	other threads:[~2022-03-01 12:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28 22:36 [PATCH] mmc: host: dw-mmc-rockchip: avoid logspam when cd-broken Peter Geis
2022-03-01 11:23 ` Robin Murphy
2022-03-01 11:49   ` Peter Geis
2022-03-01 12:38     ` Robin Murphy [this message]
2022-03-01 12:46       ` Peter Geis
2022-03-01 14:49         ` Peter Geis
2022-03-01 16:03           ` Robin Murphy
2022-03-02 10:22           ` Ulf Hansson
2022-03-02  1:03 ` Shawn Lin
2022-03-02  1:21   ` Peter Geis

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=54b24f3d-3762-abbd-5ac4-dc5728f2fe4e@arm.com \
    --to=robin.murphy@arm.com \
    --cc=heiko@sntech.de \
    --cc=jh80.chung@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=pgwipeout@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