From: patchwork-bot+linux-amlogic@kernel.org
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: linux-amlogic@lists.infradead.org, khilman@kernel.org
Subject: Re: [PATCH] mmc: meson-mx-sdio: trigger a soft reset after a timeout or CRC error
Date: Tue, 07 Jul 2020 18:51:12 +0000 [thread overview]
Message-ID: <159414787274.3387.6774407965149983621.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20200503222805.2668941-1-martin.blumenstingl@googlemail.com>
Hello:
This patch was applied to khilman/linux-amlogic.git (refs/heads/for-next).
On Mon, 4 May 2020 00:28:05 +0200 you wrote:
> The vendor driver (from the 3.10 kernel) triggers a soft reset every
> time before starting a new command. While this fixes a problem where
> SDIO cards are not detected at all (because all commands simply
> timed out) this hurts SD card read performance a bit (in my tests
> between 10% to 20%).
>
> Trigger a soft reset after we got a CRC error or if the previous command
> timed out (just like the vendor driver from the same 3.10 kernel for the
> newer SDHC controller IP does). This fixes detection of SDIO cards and
> doesn't hurt SD card read performance at the same time.
>
> [...]
Here is a summary with links:
- mmc: meson-mx-sdio: trigger a soft reset after a timeout or CRC error
https://git.kernel.org/khilman/linux-amlogic/c/91995b904ec2e44b5c159ac6a5d3f154345a4de7
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/pwbot
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2020-07-07 18:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 22:28 [PATCH] mmc: meson-mx-sdio: trigger a soft reset after a timeout or CRC error Martin Blumenstingl
2020-05-03 22:28 ` Martin Blumenstingl
2020-05-03 22:28 ` Martin Blumenstingl
2020-05-07 9:29 ` Ulf Hansson
2020-05-07 9:29 ` Ulf Hansson
2020-05-07 9:29 ` Ulf Hansson
2020-05-07 21:14 ` Martin Blumenstingl
2020-05-07 21:14 ` Martin Blumenstingl
2020-05-07 21:14 ` Martin Blumenstingl
2020-05-08 3:52 ` Ulf Hansson
2020-05-08 3:52 ` Ulf Hansson
2020-05-08 3:52 ` Ulf Hansson
2020-07-07 18:51 ` patchwork-bot+linux-amlogic [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=159414787274.3387.6774407965149983621.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-amlogic@kernel.org \
--cc=khilman@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.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.