From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Linux MMC List <linux-mmc@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Ulrich Hecht <uli+renesas@fpond.eu>,
Simon Horman <horms+renesas@verge.net.au>,
Niklas Soderlund <niklas.soderlund@ragnatech.se>
Subject: Re: [PATCH 1/2] mmc: tmio: Further fixup runtime PM management at remove
Date: Wed, 20 May 2020 22:32:18 +0200 [thread overview]
Message-ID: <20200520203111.GA4634@kunai> (raw)
In-Reply-To: <CAMuHMdUdT7MJkArMNcuX-uaryqR3qALfJSDJapBaXy8F6isffQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
> Commit 9b0d6855e756b60d ("mmc: renesas_sdhi: enforce manual correction
> for Gen3") fixed it. However, there must be other later changes that
> have impact, as reverting 9b0d6855e756b60d and reapplying 7a7dab237027
> on both mmc/next~3 and mmc/next gives a working system.
>
> Let's call it a day, no more bisecting today...
Thanks for the work, Geert!
This non-deterministic outcome already convinces me that we should
really first try to reproduce and fix the stalled SCC case before we
remove the workaround again.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-20 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 15:24 [PATCH 1/2] mmc: tmio: Further fixup runtime PM management at remove Ulf Hansson
2020-05-20 11:35 ` Ulf Hansson
2020-05-20 14:30 ` Geert Uytterhoeven
2020-05-20 15:18 ` Ulf Hansson
2020-05-20 15:49 ` Wolfram Sang
2020-05-20 18:19 ` Geert Uytterhoeven
2020-05-20 19:29 ` Geert Uytterhoeven
2020-05-20 20:32 ` Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-15 14:04 Ulf Hansson
2020-05-15 15:02 ` Ulf Hansson
2020-05-18 20:02 ` Wolfram Sang
2020-05-19 13:56 ` Wolfram Sang
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=20200520203111.GA4634@kunai \
--to=wsa+renesas@sang-engineering.com \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-mmc@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=ulf.hansson@linaro.org \
--cc=uli+renesas@fpond.eu \
--cc=yamada.masahiro@socionext.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.