From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Olliver Schinagl <oliver+list@schinagl.nl>
Cc: dev@linux-sunxi.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Hans de Goede <hdegoede@redhat.com>,
"Tsvetan Usunov, OLIMEX Ltd" <usunov@olimex.com>
Subject: Re: Almost certainly confirmed, sun7i-a20 does not support 8 bit mmc.
Date: Wed, 9 Sep 2015 16:30:38 +0200 [thread overview]
Message-ID: <20150909143038.GE9885@lukather> (raw)
In-Reply-To: <55F02E4B.70708@schinagl.nl>
[-- Attachment #1: Type: text/plain, Size: 2859 bytes --]
On Wed, Sep 09, 2015 at 03:04:11PM +0200, Olliver Schinagl wrote:
> Hey all,
>
> After experimenting with a Micron eMMC chip, I made some interesting finds I
> wanted to share with you all.
>
> For a while now, some had hopes or guessed that the A20 could have support
> for 8 bit wide bused on the SDC2. Reason for thinking this was, because the
> sun7i uses the same IP as the sun5i which does support 8 bit wide eMMC. The
> usermanual does mention 1/4/8 bit data buses and jedec 4.3 support of the
> MMC spec. Unfortunately so far, it appears that the extra data pins have not
> been muxed out to the PC pads.
>
> I used the following code to enable the extra pins on the A20:
> mmc2_pins_a: mmc2@0 {
> - allwinner,pins = "PC6", "PC7", "PC8",
> - "PC9", "PC10", "PC11";
> + allwinner,pins = "PC6", "PC7",
> + "PC8", "PC9", "PC10",
> "PC11",
> + "PC12", "PC13", "PC14",
> "PC15";
>
> and
> SUNXI_PIN(SUNXI_PINCTRL_PIN(C, 12),
> SUNXI_FUNCTION(0x0, "gpio_in"),
> SUNXI_FUNCTION(0x1, "gpio_out"),
> - SUNXI_FUNCTION(0x2, "nand0")), /* NDQ4 */
> + SUNXI_FUNCTION(0x2, "nand0"), /* NDQ4 */
> + SUNXI_FUNCTION(0x3, "mmc2")), /* D4 */
> SUNXI_PIN(SUNXI_PINCTRL_PIN(C, 13),
> SUNXI_FUNCTION(0x0, "gpio_in"),
> SUNXI_FUNCTION(0x1, "gpio_out"),
> - SUNXI_FUNCTION(0x2, "nand0")), /* NDQ5 */
> + SUNXI_FUNCTION(0x2, "nand0"), /* NDQ5 */
> + SUNXI_FUNCTION(0x3, "mmc2")), /* D5 */
> SUNXI_PIN(SUNXI_PINCTRL_PIN(C, 14),
> SUNXI_FUNCTION(0x0, "gpio_in"),
> SUNXI_FUNCTION(0x1, "gpio_out"),
> - SUNXI_FUNCTION(0x2, "nand0")), /* NDQ6 */
> + SUNXI_FUNCTION(0x2, "nand0"), /* NDQ6 */
> + SUNXI_FUNCTION(0x3, "mmc2")), /* D6 */
> SUNXI_PIN(SUNXI_PINCTRL_PIN(C, 15),
> SUNXI_FUNCTION(0x0, "gpio_in"),
> SUNXI_FUNCTION(0x1, "gpio_out"),
> - SUNXI_FUNCTION(0x2, "nand0")), /* NDQ7 */
> + SUNXI_FUNCTION(0x2, "nand0"), /* NDQ7 */
> + SUNXI_FUNCTION(0x3, "mmc2")), /* D7 */
Where did you get that info from ? Those pins have never been reported
as having the mmc2 function, which would explain why it doesn't work.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-09-09 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 13:04 Almost certainly confirmed, sun7i-a20 does not support 8 bit mmc Olliver Schinagl
2015-09-09 14:30 ` Maxime Ripard [this message]
2015-09-09 15:32 ` Hans de Goede
2015-09-09 15:56 ` [linux-sunxi] " Olliver Schinagl
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=20150909143038.GE9885@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=dev@linux-sunxi.org \
--cc=hdegoede@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver+list@schinagl.nl \
--cc=usunov@olimex.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