From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Linux MMC List <linux-mmc@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH] mmc: tmio: remove workaround for NON_REMOVABLE
Date: Thu, 21 Nov 2019 09:57:02 +0100 [thread overview]
Message-ID: <20191121085702.GA1184@ninjato> (raw)
In-Reply-To: <CAMuHMdV+W62MkSRuYZNT0ezOt_KkyStfoeZohu7m1pOP=4a0HQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]
Hi Geert,
> So some of my local code on top must have impacted the behavior.
Any change in temperature? Niklas and I wonder if it is thermal related.
> > I am working on an issue where the SCC hangs, but this has to do with
> > always providing the SCC clock (SDnH). I don't really see the connection
> > of that to RuntimePM yet, though :/
>
> Makes sense: this is consistent with the behavior when accessing
> registers without enabling the corresponding module clock: it hangs.
> So this can happen with other clocks, too.
> One more reason not to delegate clock handling to a guest, as doing it
> wrong can take down the host, too...
You mean when it comes to virtualization?
> > Can you test this simple workaround patch instead of the revert just so
> > we get an idea if these issues are related?
>
> Thanks, applying your workaround on top of
> renesas-drivers-2019-11-19-v5.4-rc8 fixes the issue.
Ok, good to know thanks for testing. Currently, I wonder why reverting
the NON_REMOVABLE workaround makes a difference. Maybe it is not
temperature related but a some race with RPM? I am debugging in this
direction now. But the lockup is still hard to trigger for me. Tried
v5.4-rc8 + NON_REMOVABLE patch with no luck. Will try renesas-drivers
next.
> This fix is part of renesas/topic/sdhi-manual-calib, right?
Yes.
> And thus has been present in some renesas-drivers release, but was
> dropped _before_ the 2019-10-15-v5.4-rc3 release.
That would explain why it didn't show up before, right? And don't you
have a Ebisu in your board farm, too? Luckily, I have one, too, now. It
should be affected.
Thanks for the pointers,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-11-21 8:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 18:36 [PATCH] mmc: tmio: remove workaround for NON_REMOVABLE Wolfram Sang
2019-10-03 10:01 ` Ulf Hansson
2019-11-19 15:51 ` Geert Uytterhoeven
2019-11-19 20:47 ` Wolfram Sang
2019-11-20 7:46 ` Geert Uytterhoeven
2019-11-21 8:57 ` Wolfram Sang [this message]
2019-11-21 9:35 ` Geert Uytterhoeven
2019-11-21 10:29 ` Ulf Hansson
2019-11-21 10:52 ` Geert Uytterhoeven
2019-11-21 11:12 ` Wolfram Sang
2019-11-21 11:10 ` Wolfram Sang
2019-12-02 8:20 ` Wolfram Sang
2019-12-02 8:31 ` Geert Uytterhoeven
2019-12-02 8:50 ` Wolfram Sang
-- strict thread matches above, loose matches on Subject: below --
2021-02-18 11:02 Wolfram Sang
2021-03-02 10:38 ` Ulf Hansson
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=20191121085702.GA1184@ninjato \
--to=wsa@the-dreams.de \
--cc=geert@linux-m68k.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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