From: khilman@baylibre•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: mt1873-evb: MMC failing with linux-next
Date: Mon, 08 Feb 2016 17:18:55 -0800 [thread overview]
Message-ID: <7hegcmadfk.fsf@baylibre.com> (raw)
Hello,
I tried getting MMC working with linux-next (next-20160208) on
mt8173-evb by enabling a few options[1] on top of the default defconfig,
and this results in a kernel that hangs as soon as it starts userspace.
The MMC driver seems to start, though has some regulator issues:
[ 0.526380] sdhci: Secure Digital Host Controller Interface driver
[ 0.527176] sdhci: Copyright(c) Pierre Ossman
[ 0.528835] vio18: unsupportable voltage range: 3300000-1980000uV
[ 0.529610] mtk-msdc 11230000.mmc: Regulator set error -22: 3300000 - 3300000
[ 0.563731] mtk-msdc 11240000.mmc: Got CD GPIO
The driver appears to be attempting to set 3.3V but using a 1.8V
regulator (vio18), which is failing.
Then, the kernel hangs after freeing unused memory:
[ 0.616386] hctosys: unable to open rtc device (rtc0)
[ 0.624118] usb_vbus: disabling
[ 0.624547] vusb: disabling
[ 0.624929] vgp6: disabling
[ 0.625635] ALSA device list:
[ 0.626009] No soundcards found.
[ 0.626963] Freeing unused kernel memory: 724K (ffffffc000977000 - ffffffc000a2c000)
And nothing further here.
It boots fine when disabling the MMC driver (CONFIG_MMC_MTK=n).
Any ideas?
Kevin
[1]
CONFIG_MMC_MTK=y
CONFIG_MFD_MT6397=y
CONFIG_REGULATOR_MT6397=y
CONFIG_MTK_PMIC_WRAP=y
next reply other threads:[~2016-02-09 1:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 1:18 Kevin Hilman [this message]
[not found] ` <56BDF937.60208@gmail.com>
2016-02-12 15:28 ` mt1873-evb: MMC failing with linux-next Matthias Brugger
2016-02-12 16:01 ` Matthias Brugger
2016-02-12 21:42 ` Kevin Hilman
2016-02-15 3:52 ` Eddie Huang
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=7hegcmadfk.fsf@baylibre.com \
--to=khilman@baylibre$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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