From: Holger Schurig <holgerschurig@gmail.com>
To: linux-mmc@vger.kernel.org
Subject: BUG 4.4rc-4: wrong eMMC signaling voltage reported
Date: Wed, 09 Dec 2015 15:53:06 +0100 [thread overview]
Message-ID: <87fuzbvfl9.fsf@gmail.com> (raw)
Hi,
I have an i.MX6Q based system that cannot provide 1.8V voltage towards
the eMMC. But Linux 4.4-rc4 reports 1.8V for the eMMC, but this is
impossible. Neither my hardware allows this, nor does the DT say it.
root@imx6q:/sys/kernel/debug# cat mmc1/ios
clock: 52000000 Hz
actual clock: 49500000 Hz
vdd: 21 (3.3 ~ 3.4 V)
bus mode: 2 (push-pull)
chip select: 0 (don't care)
power mode: 2 (on)
bus width: 3 (8 bits)
timing spec: 8 (mmc DDR52)
signal voltage: 0 (1.80 V)
driver type: 0 (driver type B)
My device tree however tells that I don't have 1.8V:
/* this is the built in eMMC */
&usdhc4 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_usdhc4>;
bus-width = <8>;
non-removable;
vmmc-supply = <®_3p3v>;
max-frequency = <198000000>;
no-1-8-v;
status = "okay";
};
Fun fact: for the SDCARD things are correctly reported:
root@imx6q:/sys/kernel/debug# cat mmc1/ios
clock: 36000000 Hz
actual clock: 33000000 Hz
vdd: 21 (3.3 ~ 3.4 V)
bus mode: 2 (push-pull)
chip select: 0 (don't care)
power mode: 2 (on)
bus width: 2 (4 bits)
timing spec: 2 (sd high-speed)
signal voltage: 0 (3.30 V)
driver type: 0 (driver type B)
And here my device tree excerpt:
/* this is the SDCARD slot */
&usdhc2 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_usdhc2>;
cd-gpios = <&gpio1 2 GPIO_ACTIVE_LOW>;
wp-gpios = <&gpio1 4 GPIO_ACTIVE_HIGH>;
vmmc-supply = <®_3p3v>;
max-frequency = <36000000>;
no-1-8-v;
status = "okay";
};
next reply other threads:[~2015-12-09 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 14:53 Holger Schurig [this message]
2015-12-17 16:10 ` BUG 4.4rc-4: wrong eMMC signaling voltage reported Ulf Hansson
2015-12-22 8:33 ` Holger Schurig
2015-12-22 9:18 ` Ulf Hansson
2015-12-22 9:39 ` Fabio Estevam
2015-12-22 10:28 ` Ulf Hansson
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=87fuzbvfl9.fsf@gmail.com \
--to=holgerschurig@gmail.com \
--cc=linux-mmc@vger.kernel.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.