From: Wolfram Sang <wsa@the-dreams.de>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Cc: Simon Horman <horms+renesas@verge.net.au>,
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,
Ai Kyuse <ai.kyuse.uw@renesas.com>
Subject: Re: [PATCH v8 6/6] mmc: sh_mobile_sdhi: Add tuning support
Date: Mon, 23 Jan 2017 12:16:39 +0100 [thread overview]
Message-ID: <20170123111639.nymy775co2uckxu2@ninjato> (raw)
In-Reply-To: <20170110210848.GA25542@bigcity.dyn.berto.se>
[-- Attachment #1: Type: text/plain, Size: 1876 bytes --]
Hi Niklas,
so I scratched my head around this a little more... I don't have an
explanation, but want to highlight some interesting points:
> [ 2.954859] mmc0: new ultra high speed SDR50 SDHC card at address aaaa
So, this is an SDR50 card. The patch in questions adds tuning support
which is only needed for SDR104. The whole tuning procedure is not (or
at least should not be) exercised.
> Oddly enough the error are only printed when I insert the SD card in the
> mmc0 slot. I can insert/eject the card multiple times in mmc1 and no
> error but the first insertion in mmc0 and boom. Only difference I can
> see are the clock speed between mmc0 and mmc1.
That actually makes sense. mmc0 is SDR104 capable and has the SCC unit
which is needed for tuning (note the larger register space in the dtsi).
The other mmc cores do only SDR50 and do not have an SCC. Because your
warning is about a broken pointer, I wonder if it is about accessing
SCC? Maybe in hw_reset? Wild guess, though. On the other hand, the
register ranges in the dtsi look ok, so I'd assume the IPMMU should have
all the info it needs? But I don't really know...
First thing to try: please remove the property "sd-uhs-sdr104;" from
your Koelsch DTS. I'd expect this makes the warnings go away. If so,
readd the property and instrument if sh_mobile_sdhi_hw_reset() gets
called. One outcome might be that the printouts might be tied to the
warnings.
> I can interact fine with the card (I tried checksumming a large file and
> compared with a known good) so it's not broken. I can also interact with
> other devices using the DMAC+IPMMU without similar warnings being
> printed at all, I tested with i2c6.
That is relieving and also makes sense in the way that nothing in this
patch should be needed to get an SDR50 card running.
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-01-23 11:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 14:15 [PATCH v8 0/6] UHS-I SDR-104 support for sh_mobile_sdhi Simon Horman
2016-11-03 14:15 ` [PATCH v8 1/6] mmc: core: Add helper to see if a host can be retuned Simon Horman
2016-11-03 14:16 ` [PATCH v8 2/6] mmc: tmio: enhance illegal sequence handling Simon Horman
2016-11-03 14:16 ` [PATCH v8 3/6] mmc: tmio: document mandatory and optional callbacks Simon Horman
2016-11-03 14:16 ` [PATCH v8 4/6] mmc: tmio: Add hw reset support Simon Horman
2016-11-03 14:16 ` [PATCH v8 5/6] mmc: tmio: Add tuning support Simon Horman
2016-11-03 14:16 ` [PATCH v8 6/6] mmc: sh_mobile_sdhi: " Simon Horman
2017-01-10 21:08 ` Niklas Söderlund
2017-01-10 22:30 ` Wolfram Sang
2017-01-11 8:35 ` Niklas Söderlund
2017-01-11 8:42 ` Geert Uytterhoeven
2017-01-11 9:17 ` Niklas Söderlund
2017-01-11 15:05 ` Wolfram Sang
2017-01-11 15:57 ` Niklas Söderlund
2017-01-11 15:59 ` Geert Uytterhoeven
2017-01-11 17:34 ` Wolfram Sang
2017-01-12 11:17 ` Niklas Söderlund
2017-01-12 11:23 ` Geert Uytterhoeven
2017-01-12 13:03 ` Wolfram Sang
2017-01-17 11:29 ` Niklas Söderlund
2017-01-23 11:16 ` Wolfram Sang [this message]
2017-01-31 20:56 ` Niklas Söderlund
2017-01-26 9:58 ` Simon Horman
2016-11-10 11:45 ` [PATCH v8 0/6] UHS-I SDR-104 support for sh_mobile_sdhi Wolfram Sang
2016-11-10 22:21 ` Ulf Hansson
2016-11-11 7:20 ` 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=20170123111639.nymy775co2uckxu2@ninjato \
--to=wsa@the-dreams.de \
--cc=ai.kyuse.uw@renesas.com \
--cc=horms+renesas@verge.net.au \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=niklas.soderlund@ragnatech.se \
--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