From: Maxime Ripard <maxime.ripard@bootlin.com>
To: "Alejandro González" <alejandro.gonzalez.correo@gmail.com>
Cc: ulf.hansson@linaro.org, wens@csie.org, linus.walleij@linaro.org,
gregkh@linuxfoundation.org, tglx@linutronix.de,
linux-mmc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: Re: [PATCH] mmc: sunxi: fix unusuable eMMC on some H6 boards by disabling DDR
Date: Tue, 27 Aug 2019 15:32:11 +0200 [thread overview]
Message-ID: <20190827133211.g5n4uasyz2yvjpjr@flea> (raw)
In-Reply-To: <20190825150558.15173-1-alejandro.gonzalez.correo@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]
On Sun, Aug 25, 2019 at 05:05:58PM +0200, Alejandro González wrote:
> Some Allwinner H6 boards have timing problems when dealing with
> DDR-capable eMMC cards. These boards include the Pine H64 and Tanix TX6.
>
> These timing problems result in out of sync communication between the
> driver and the eMMC, which renders the memory unsuable for every
> operation but some basic commmands, like reading the status register.
>
> The cause of these timing problems is not yet well known, but they go
> away by disabling DDR mode operation in the driver. Like on some H5
> boards, it might be that the traces are not precise enough to support
> these speeds. However, Jernej Skrabec compared the BSP driver with this
> driver, and found that the BSP driver configures pinctrl to operate at
> 1.8 V when entering DDR mode (although 3.3 V operation is supported), while
> the mainline kernel lacks any mechanism to switch voltages dynamically.
> Finally, other possible cause might be some timing parameter that is
> different on the H6 with respect to other SoCs.
This should be a comment in the driver where this is disabled.
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-08-27 13:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 15:05 Alejandro González
2019-08-27 13:24 ` Ulf Hansson
2019-08-28 10:52 ` Alejandro González
2019-08-29 11:37 ` Ulf Hansson
2019-08-27 13:32 ` Maxime Ripard [this message]
2019-08-28 12:52 ` Linus Walleij
2019-08-28 13:29 ` [linux-sunxi] " Chen-Yu Tsai
2019-08-28 13:43 ` Maxime Ripard
2019-08-28 13:46 ` Chen-Yu Tsai
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=20190827133211.g5n4uasyz2yvjpjr@flea \
--to=maxime.ripard@bootlin.com \
--cc=alejandro.gonzalez.correo@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=ulf.hansson@linaro.org \
--cc=wens@csie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®