From: Wolfram Sang <wsa@the-dreams.de>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>,
Yasushi SHOJI <yashi@atmark-techno.com>,
Masaharu Hayakawa <masaharu.hayakawa.ry@renesas.com>
Subject: Re: [RFT PATCH] mmc: tmio: make sure SDIO gets reinitialized after resume
Date: Tue, 23 May 2017 14:23:39 +0200 [thread overview]
Message-ID: <20170523122339.GA3747@katana> (raw)
In-Reply-To: <TY1PR06MB0992573FB717D7C90373F1FDD8F90@TY1PR06MB0992.apcprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
Shimoda-san,
> > This patch addresses a report I got from Shimoda-san. I can't really test it
> > because the SDIO cards I have all require MMC_PM_KEEP_POWER to suspend and
> > that we don't support. So, I send this out to ask for testing. At least it
> > didn't cause regressions for the setup I used. To make testing easier, this
> > is *not* put on top of Simon's SDHI DMA rework patches, so it should apply
> > on current upstream and development branches.
>
> Thank you for the patch!
> Hayakawa-san tested this patch on both H3/Salvator-X and E2/ALT.
>
> So,
> Tested-by: Masaharu Hayakawa <masaharu.hayakawa.ry@renesas.com>
Very good, thanks, also to Hayakawa-san! I'll rebase this patch and
resubmit with the tag added!
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-05-23 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 12:30 [RFT PATCH] mmc: tmio: make sure SDIO gets reinitialized after resume Wolfram Sang
2017-05-23 12:15 ` Yoshihiro Shimoda
2017-05-23 12:23 ` Wolfram Sang [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=20170523122339.GA3747@katana \
--to=wsa@the-dreams.de \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=masaharu.hayakawa.ry@renesas.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=yashi@atmark-techno.com \
--cc=yoshihiro.shimoda.uh@renesas.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