From: Wolfram Sang <wsa@the-dreams.de>
To: Simon Horman <horms@verge.net.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH RESEND 0/2] arm64: gen3: enable eMMC HS200 in DT
Date: Thu, 26 Jan 2017 15:16:57 +0100 [thread overview]
Message-ID: <20170126141656.GD2718@katana> (raw)
In-Reply-To: <20170126140643.GA11104@verge.net.au>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
> I have tested with "the new mmc/next" and things seem better.
Good. The issue you saw is expected when you have not the enablement
patches in place.
> I am still of a mind to drop the M3-W patch of this series because unless
> we can control the order that things are merged into Linus's tree
> there will be a temporary regression there. Moreover I'm not very excited
> about renesas-next having regressed.
I have not heard of a regression. Geert, did you report that? Did I miss
that? As you can see, I did test the patches with M3 as well:
http://elinux.org/Tests:eMMC-HS
and Jinso test team (Duc-san) confirmed it works for them with H3 and
M3-W. In private communication, though.
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-01-26 14:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 17:39 [PATCH RESEND 0/2] arm64: gen3: enable eMMC HS200 in DT Wolfram Sang
2017-01-04 17:39 ` [PATCH RESEND 1/2] arm64: dts: r8a7795: enable HS200 for eMMC Wolfram Sang
2017-01-04 17:39 ` [PATCH RESEND 2/2] arm64: dts: r8a7796: " Wolfram Sang
2017-01-12 22:43 ` [PATCH RESEND 0/2] arm64: gen3: enable eMMC HS200 in DT Wolfram Sang
2017-01-13 8:37 ` Simon Horman
2017-01-13 8:39 ` Wolfram Sang
2017-01-26 10:01 ` Simon Horman
2017-01-26 10:03 ` Wolfram Sang
2017-01-26 10:27 ` Simon Horman
2017-01-26 11:36 ` Wolfram Sang
2017-01-26 13:33 ` Simon Horman
2017-01-26 13:54 ` Wolfram Sang
2017-01-26 14:06 ` Simon Horman
2017-01-26 14:16 ` Wolfram Sang [this message]
2017-01-26 14:40 ` Geert Uytterhoeven
2017-01-26 14:51 ` Wolfram Sang
2017-01-26 15:24 ` Simon Horman
2017-01-26 20:17 ` Wolfram Sang
2017-01-27 6:33 ` Simon Horman
2017-01-27 7:27 ` Wolfram Sang
2017-01-27 8:16 ` Simon Horman
2017-04-08 11:06 ` Wolfram Sang
2017-04-08 11:20 ` Wolfram Sang
2017-01-26 13:58 ` Geert Uytterhoeven
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=20170126141656.GD2718@katana \
--to=wsa@the-dreams.de \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
/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.