From: Wolfram Sang <wsa@the-dreams.de>
To: Simon Horman <horms@verge.net.au>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Magnus Damm <magnus.damm@gmail.com>,
linux-mmc@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v5 10/11] arm64: dts: r8a7795: salvator-x: Enable UHS-I SDR-104
Date: Thu, 1 Sep 2016 16:29:43 +0200 [thread overview]
Message-ID: <20160901142943.GC4824@katana> (raw)
In-Reply-To: <20160901142539.GI14300@verge.net.au>
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
On Thu, Sep 01, 2016 at 04:25:40PM +0200, Simon Horman wrote:
> On Thu, Sep 01, 2016 at 09:23:54AM +0200, Wolfram Sang wrote:
> > On Tue, Aug 30, 2016 at 11:09:58PM +0200, Simon Horman wrote:
> > > Add the sd-uhs-sdr104 property to SDHI0 and SDHI1.
> > >
> > > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> >
> > After removing a SDR104 card from the slot, the interface is stalled
> > here. No new cards (even non-SDR104) can be detected anymore, sadly.
> > Happens for both slots on my H3 Salvator-X.
>
> Bother. That is rather difficult for me to exercise.
> Does this occur without sdr104 enabled (e.g. in DT)?
No, then it works fine.
I'll try to get you more information. Might be not before Monday,
though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-01 14:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 21:09 [PATCH v5 00/11] UHS-I SDR-104 support for sh_mobile_sdhi Simon Horman
2016-08-30 21:09 ` [PATCH v5 01/11] mmc: tmio: enhance illegal sequence handling Simon Horman
2016-08-30 21:09 ` [PATCH v5 02/11] mmc: tmio: document mandatory and optional callbacks Simon Horman
2016-08-30 21:09 ` [PATCH v5 03/11] mmc: tmio: Add hw reset support Simon Horman
2016-08-31 7:50 ` Ulf Hansson
2016-09-01 6:45 ` Simon Horman
2016-08-30 21:09 ` [PATCH v5 04/11] mmc: tmio: Add tuning support Simon Horman
2016-08-30 21:09 ` [PATCH v5 05/11] mmc: sh_mobile_sdhi: " Simon Horman
2016-08-30 21:09 ` [PATCH v5 06/11] ARM: dts: lager: Enable UHS-I SDR-104 Simon Horman
2016-08-30 21:09 ` [PATCH v5 07/11] arm64: dts: r8a7795: remove unnecessary cap-mmc-highspeed property Simon Horman
2016-09-01 14:32 ` Simon Horman
2016-09-16 10:29 ` Wolfram Sang
2016-08-30 21:09 ` [PATCH v5 08/11] arm64: r8a7795: Set maximum frequencies for SDHI clocks Simon Horman
2016-08-31 8:44 ` Wolfram Sang
2016-09-01 14:24 ` Simon Horman
2016-08-30 21:09 ` [PATCH v5 09/11] arm64: dts: r8a7795: salvator: enable UHS for SDHI 0 & 3 Simon Horman
2016-08-30 21:09 ` [PATCH v5 10/11] arm64: dts: r8a7795: salvator-x: Enable UHS-I SDR-104 Simon Horman
2016-09-01 7:23 ` Wolfram Sang
2016-09-01 14:25 ` Simon Horman
2016-09-01 14:29 ` Wolfram Sang [this message]
2016-09-01 14:37 ` Simon Horman
2016-08-30 21:09 ` [PATCH v5 11/11] arm64: defconfig: Enable SDHI and GPIO_REGULATOR Simon Horman
2016-09-01 14:33 ` Simon Horman
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=20160901142943.GC4824@katana \
--to=wsa@the-dreams.de \
--cc=horms@verge.net.au \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=ulf.hansson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).