From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/4] arm64: add support for i.MX8M EVK board
Date: Fri, 23 Feb 2018 23:03:53 +0800 [thread overview]
Message-ID: <20180223150352.GU3217@dragon> (raw)
In-Reply-To: <20180201183126.32384-3-l.stach@pengutronix.de>
On Thu, Feb 01, 2018 at 07:31:25PM +0100, Lucas Stach wrote:
> +&usdhc1 {
> + pinctrl-names = "default", "state_100mhz", "state_200mhz";
> + pinctrl-0 = <&pinctrl_usdhc1_cd_reset>, <&pinctrl_usdhc1_clk_strobe>,
> + <&pinctrl_usdhc1_data>;
> + pinctrl-1 = <&pinctrl_usdhc1_cd_reset>,
> + <&pinctrl_usdhc1_clk_strobe_100mhz>,
> + <&pinctrl_usdhc1_data_100mhz>;
> + pinctrl-2 = <&pinctrl_usdhc1_cd_reset>,
> + <&pinctrl_usdhc1_clk_strobe_200mhz>,
> + <&pinctrl_usdhc1_data_200mhz>;
> + vqmmc-supply = <&sw4_reg>;
> + bus-width = <8>;
> + non-removable;
> + no-sd;
> + no-sdio;
> + status = "okay";
> +};
I'm not sure it can be enabled right now. Per my testing, eMMC is not
working yet.
[ 0.879756] mmc0: Switching to 3.3V signalling voltage failed
[ 0.913587] mmc0: SDHCI controller on 30b40000.usdhc [30b40000.usdhc] using ADMA
...
[ 1.007628] mmc0: switch to high-speed from hs200 failed, err:-110
[ 1.013873] mmc0: error -110 whilst initialising MMC card
[ 1.020639] mmc0: Switching to 3.3V signalling voltage failed
...
[ 1.132462] mmc0: switch to high-speed from hs200 failed, err:-110
[ 1.138674] mmc0: error -110 whilst initialising MMC card
[ 1.145394] mmc0: Switching to 3.3V signalling voltage failed
[ 1.268367] mmc0: switch to high-speed from hs200 failed, err:-110
[ 1.274576] mmc0: error -110 whilst initialising MMC card
[ 1.281291] mmc0: Switching to 3.3V signalling voltage failed
[ 1.440708] mmc0: switch to high-speed from hs200 failed, err:-110
[ 1.446919] mmc0: error -110 whilst initialising MMC card
Or am I missing anything?
Shawn
next prev parent reply other threads:[~2018-02-23 15:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 18:31 [PATCH v2 1/4] arm64: add basic Kconfig symbols for i.MX8 Lucas Stach
2018-02-01 18:31 ` [PATCH v2 2/4] arm64: add basic DTS for i.MX8MQ Lucas Stach
2018-02-02 8:13 ` Jacky Bai
2018-02-05 8:45 ` Shawn Guo
2018-02-05 9:07 ` Jacky Bai
2018-02-05 6:09 ` Rob Herring
2018-02-05 15:00 ` Marc Zyngier
2018-02-25 10:47 ` A.s. Dong
2018-02-26 3:17 ` Shawn Guo
2018-02-26 6:52 ` A.s. Dong
2018-02-26 7:09 ` Shawn Guo
2018-02-26 8:07 ` A.s. Dong
2018-03-09 3:23 ` Shawn Guo
2018-02-01 18:31 ` [PATCH v2 3/4] arm64: add support for i.MX8M EVK board Lucas Stach
2018-02-05 6:09 ` Rob Herring
2018-02-05 7:24 ` Baruch Siach
2018-02-05 11:10 ` Lucas Stach
2018-02-23 3:46 ` Shawn Guo
2018-02-23 4:32 ` Baruch Siach
2018-02-23 7:05 ` Shawn Guo
2018-02-23 15:03 ` Shawn Guo [this message]
2018-02-23 15:30 ` Juergen Borleis
2018-02-23 15:46 ` Lucas Stach
2018-02-24 2:58 ` Bough Chen
2018-02-24 6:00 ` Shawn Guo
2018-02-25 9:54 ` A.s. Dong
2018-02-23 15:45 ` Lucas Stach
2018-02-25 10:00 ` A.s. Dong
2018-02-01 18:31 ` [PATCH v2 4/4] MAINTAINERS: add i.MX8 DT path to i.MX architecture Lucas Stach
2018-02-23 14:56 ` [PATCH v2 1/4] arm64: add basic Kconfig symbols for i.MX8 Shawn Guo
2018-02-25 10:17 ` A.s. Dong
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=20180223150352.GU3217@dragon \
--to=shawnguo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).