From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Chen-Yu Tsai <wens@csie.org>, linux-mmc@vger.kernel.org
Subject: Re: sunxi mmc on A10 / A13 does not have a sample clock, cannot do ddr ?
Date: Tue, 5 Jul 2016 10:29:22 +0200 [thread overview]
Message-ID: <20160705082922.GJ7643@lukather> (raw)
In-Reply-To: <de974dc5-2192-a87f-d727-a8e9e9f4b079@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
On Sun, Jul 03, 2016 at 05:20:43PM +0200, Hans de Goede wrote:
> Hi Chen-Yu,
>
> While working on some dts cleanups I tested
> the latest sunxi-next kernel code on my A13
> Utoo P66 tablet and the emmc no longer works.
>
> The kernel tries to enable DDR52 mode on it,
> since it apparently can do that and after that
> the kernel can no longer talk to it.
>
> Removing MMC_CAP_1_8V_DDR from sunxi-mmc.c
> fixes this.
>
> Part of the problem likely is that it seems
> that the mmc clock on sun4i / sun5i do
> not have sample / output phase clks.
>
> It does not matter what one writes to
> 0x1c20088 / 0x1c20090, bits 8-10 and
> 20-22 are always 0.
>
> I've observed this on both sun4i and sun5i,
> and the sun4i / sun5i datasheets
> also do not mention the phase bits
> for register 0x1c20088 / 0x1c20090.
>
> As such I'm thinking that the best way to fix
> this is:
>
> 1) In sunxi-mmc.c make the sample clocks
> optional; and if not present then do not
> set MMC_CAP_1_8V_DDR (and do not try to
> set sample clks)
>
> 2) Remove the sample clks from the base
> sun4i / sun5i dtsi files
That looks like the right approach to me.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-07-05 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 15:20 sunxi mmc on A10 / A13 does not have a sample clock, cannot do ddr ? Hans de Goede
2016-07-05 8:29 ` Maxime Ripard [this message]
2016-07-06 2:20 ` 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=20160705082922.GJ7643@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=hdegoede@redhat.com \
--cc=linux-mmc@vger.kernel.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 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.