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: Mon, 2 Dec 2019 09:20:41 +0100 [thread overview]
Message-ID: <20191202082041.GA1266@kunai> (raw)
In-Reply-To: <20191121111025.GB1184@ninjato>
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
> anymore. However, I know have the issue highly reproducible with
> renesas_defconfig and renesas-drivers. Good!
Bummer, it is not that reproducible :(
Yesterday, I tried latest linus tree which includes Ulf's changes to
genpd and it worked, even with the NON_REMOVABLE workaround removed
again. Then I reverted Ulf's changes to double check it made a
difference, but the SCC still worked. So, I switched back to the
renesas-drivers tree which used to fail last week, and it sadly works,
too. Sigh...
I'll move over now to upport the manual calibration mechanism and will
keep an eye on if/when the SCC fails again...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-02 8:20 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
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 [this message]
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=20191202082041.GA1266@kunai \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.